InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comFri, 24 May 2013 02:16:53 GMT20http://www.sqlservercentral.com/Forums/Topic760859-146-1.aspx[quote][b]KP (7/30/2009)[/b][hr]I ran exec sp_helpuser 'newUser' I got back UserName as newUserGroupName as db_ownerLoginName as newUserDefDBName as MyDBDefSchemaName as dboUserIdSIDPlease help.[/quote]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.Sat, 01 Aug 2009 16:20:36 GMTgeorge sibbaldhttp://www.sqlservercentral.com/Forums/Topic760859-146-1.aspx[quote][b]2 Tim 3:16 (7/31/2009)[/b][hr]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.[/quote]execute sp_change_users_login 'loginname','username'Fri, 31 Jul 2009 09:02:56 GMTSanjayAttrayhttp://www.sqlservercentral.com/Forums/Topic760859-146-1.aspxMayne 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.Fri, 31 Jul 2009 08:36:47 GMT2 Tim 3:16http://www.sqlservercentral.com/Forums/Topic760859-146-1.aspxI ran exec sp_helpuser 'newUser' I got back UserName as newUserGroupName as db_ownerLoginName as newUserDefDBName as MyDBDefSchemaName as dboUserIdSIDPlease help.Thu, 30 Jul 2009 08:50:08 GMTKP-249943http://www.sqlservercentral.com/Forums/Topic760859-146-1.aspxrun 'exec sp_helpuser ' in the database, what does that return?Tue, 28 Jul 2009 13:18:39 GMTgeorge sibbaldhttp://www.sqlservercentral.com/Forums/Topic760859-146-1.aspxI get the same result as my co-worker.Tue, 28 Jul 2009 13:14:24 GMTKP-249943http://www.sqlservercentral.com/Forums/Topic760859-146-1.aspxPerhaps 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?Tue, 28 Jul 2009 09:36:28 GMTsturnerhttp://www.sqlservercentral.com/Forums/Topic760859-146-1.aspxHi,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?Tue, 28 Jul 2009 09:25:33 GMTKP-249943