Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
We use SQL server 2008 as our RDBMS and we have a database that has a different user rather than dbo as its owner.
The problem is in one machine a stored procedure can not run unless its owner is mentioned.
If we connect to our database using this user and try to execute the following :
exec ourSP
we get a “could not find ourSP” error but this works fine:
exec user.ourSP
Does anybody knows what can lead to such a strange behavior?
It seems that If a user is checked as SysAdmin in sever security area it will have the dbo user name when a connection to a database is made and it will be treated like dbo.