|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: Friday, August 31, 2012 3:42 PM
Points: 19,
Visits: 262
|
|
Hi,
I am using SQL Server 2005 (SP3).
I created a new login via SSMS. I went to Security-->Logins-->New Login. I created a new login called newUser with a password.
Then I went to my User Database called MyDB. I went to Security-->Users-->New User. Under Login name and User Name I typed in newUser. Under the Database Role Membership I check db_owner.
Then I gave this UserID and Password to my co-worker at work. When my co-worker uses SSMS and users newUser as the UserId and the correct password, in SSMS he is unable to see MyDB. He is also unable to create new Stored Procs etc. Why is that? Once he is the db_owner he should be able to do everything on this database (including DROP). I don't want to make newUser as the Owner.
Any ideas? tips?
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: 2 days ago @ 11:56 AM
Points: 1,315,
Visits: 2,885
|
|
Perhaps your co-worker is not logging in with that user id and password. He might be connecting with integrated security.
Why don't you log in yourself with that user and password and see what you get?
The probability of survival is inversely proportional to the angle of arrival.
|
|
|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: Friday, August 31, 2012 3:42 PM
Points: 19,
Visits: 262
|
|
| I get the same result as my co-worker.
|
|
|
|
|
SSCertifiable
       
Group: General Forum Members
Last Login: Yesterday @ 12:30 PM
Points: 5,269,
Visits: 11,205
|
|
run 'exec sp_helpuser ' in the database, what does that return?
---------------------------------------------------------------------
|
|
|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: Friday, August 31, 2012 3:42 PM
Points: 19,
Visits: 262
|
|
I ran exec sp_helpuser 'newUser'
I got back UserName as newUser GroupName as db_owner LoginName as newUser DefDBName as MyDB DefSchemaName as dbo UserId SID
Please help.
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Friday, May 10, 2013 9:45 AM
Points: 1,081,
Visits: 1,453
|
|
Mayne the user didn't get matched up with the login. Go to Security - Login and look at the porperties for the login and see if the user database is checked for dbo.
Tim White
|
|
|
|
|
Hall of Fame
       
Group: General Forum Members
Last Login: Friday, March 15, 2013 2:43 PM
Points: 3,924,
Visits: 1,554
|
|
2 Tim 3:16 (7/31/2009) Mayne the user didn't get matched up with the login. Go to Security - Login and look at the porperties for the login and see if the user database is checked for dbo.
execute sp_change_users_login 'loginname','username'
SQL DBA.
|
|
|
|
|
SSCertifiable
       
Group: General Forum Members
Last Login: Yesterday @ 12:30 PM
Points: 5,269,
Visits: 11,205
|
|
KP (7/30/2009) I ran exec sp_helpuser 'newUser'
I got back UserName as newUser GroupName as db_owner LoginName as newUser DefDBName as MyDB DefSchemaName as dbo UserId SID
Please help. This looks correct.
You say this id cannot create stored procs etc but if it cannot even see the database how are you getting that far to test? Are you able to issue the use mydb command in a query window and switch to the database?
I suggest you run profiler as the id logs on and track what happens. Include errors and warnings in the trace. If its a permissions problem on some system object that will be the last command issued and the trace will stop there.
Post any erors you haave received if any because what you report so far does not add up.
---------------------------------------------------------------------
|
|
|
|