Posted by ZRexRider on 10/01/83 11:35

Dan you nailed it - SUSER_SNAME() in my trigger blows up because there
isn't a '\' and I didn't code for it.

Happy Holidays to you as well!


Dan Guzman wrote:
> Check the proc (or invoked trigger) to see SUSER_SNAME() is being parsed
> into separate domain/account components. The code may fail with a standard
> SQL Security connection because a '\' is assumed to be present.
>
> --
> Happy Holidays
>
> Dan Guzman
> SQL Server MVP
>
> "ZRexRider" <jerryg@ptd.net> wrote in message
> news:1135358521.631291.106350@g44g2000cwa.googlegroups.com...
> > Hi,
> >
> > I have a .NET application that connects to a SQL 2000 database using
> > trusted security. It eventually calls a stored procedure that receives
> > 3 parameters - nothing special.
> >
> > If I simply change the connection string to use a valid Userid and
> > Password it still connects to the DB w/o problems but when it executes
> > the SP I get the following:
> >
> > System.Data.SqlClient.SqlException: Invalid length parameter passed to
> > the substring function.
> >
> > I change nothing but the login. Same store procedure, same parameters.
> >
> > Any ideas?
> >

[Back to original message]