Unusual Stored Procedure Behavior...

[bmgmzp]

When I logged into SQL Server 2005 using windows authentication to execute a stored procedure it worked fine.

HOWEVER when I logged into SQL Server 2005 using SQL Server Authentication (the sa account) and executed the SAME stored procedure I got no results.

I have no idea why that would make ANY difference. Any advice?

Thanks

 

[gmmastros]

Were you connected to the same database?



-George

"the screen with the little boxes in the window." - Moron

 

[gmmastros]

To see what the default database is...

Select name, dbname From sys.syslogins

Select name, dbname from master..syslogins

I strongly advise that you do NOT change the default database for the sa user. It should ALWAYS be set to master. The problem is... You could change the default database for SA to a user database, and then detach the user database. If you do this, you will have a VERY difficult time logging in to SQL Server.

-George

"the screen with the little boxes in the window." - Moron

 

[tektipsFriend]

Yes I was trying to log into the same database on the same server...

Here is another clue... when i was trying to log in using Windows Authentication I was using my username (mmurphy) ... so i tried another user through windows authentication and I got this error:

Login failed for user 'Domain\WShuey'

Could that be part of the same problem?

 

[ESquared]

You can't "try another user through windows authentication." Windows authentication means to use the credential information with your Windows login. So unless you mean you logged off your computer and logged back in as a different user, then you were entering Domain\WShuey into a username/password prompt that cannot accept domain users. The username/password prompt only accepts users that are defined as standalone users on the server and in the database you are connecting to.

[COLOR=#aa88aa black]Cum catapultae proscriptae erunt tum soli proscript catapultas habebunt.[/color]