Re: question about syslogins and sysusers...
From: Tibor Karaszi (tibor_please.no.email_karaszi_at_hotmail.nomail.com)
Date: 08/09/04
- Next message: Woody Splawn: "Re: Query question"
- Previous message: Andre: "Tracing A Restore"
- In reply to: ===steve pdx===: "Re: question about syslogins and sysusers..."
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 10 Aug 2004 00:22:10 +0200
Does the sid number in sysusers exist in syslogins. Also, orphaned users can come from backup/restore or
detach/attach. Read more about that in Books Online, sp_change_users_login.
-- Tibor Karaszi, SQL Server MVP http://www.karaszi.com/sqlserver/default.asp http://www.solidqualitylearning.com/ "===steve pdx===" <lins@nospam_portptld.com> wrote in message news:%23VXAT9kfEHA.3076@TK2MSFTNGP10.phx.gbl... > it's possible that way; but in my case, it's the sql standard accounts i > have been seeing the sysuers table (with isntuser = 0), but not in syslogins > table. > > > "Graeme Malcolm" <graemem_cm@hotmail.com> wrote in message > news:OwWH9ZkfEHA.236@tk2msftngp13.phx.gbl... > > I think Tibor is on the right track here. If you've created a login for a > > Windows group, and a member of that group creates an object in a database, > a > > user is silently added to the database with the name of the Windows > account. > > > > For example: > > Suppose you have a Windows account 'MyDomain\Fred' in a group > > 'MyDomain\SqlUsers'. Create a login for the MyDomain\SqlUsers group (which > > will create an entry in syslogins) and add the group to the DDLAdmin role > in > > the Northwind database (which creates a user called SqlUsers in the > > Northwind databases sysusers table). Now, suppose Fred logs into SQL > > Server - he gets access because he's in the SqlUsers group. However, if he > > executes a CREATE TABLE statement in Northwind, he has to become the owner > > of the table - so a user called 'MyDomain\Fred' is silently created in the > > Northwind database. You now have the situation you descibe, a user with no > > matching login. > > > > That seem likely in your scenario? > > Graeme > > > > -- > > ---- > > Graeme Malcolm > > Principal Technologist > > Content Master Ltd. > > www.contentmaster.com > > www.microsoft.com/mspress/books/6137.asp > > > > > > "===steve pdx===" <lins@nospam_portptld.com> wrote in message > > news:u5cha5jfEHA.2460@TK2MSFTNGP12.phx.gbl... > > I appreciate the responses i've got, but I'd like to make my question more > > clear: > > > > there are accounts found in sysusers table(s), but not in syslogins in > > master database. Not the other way around! > > (which is ok, an account can be in syslogins but not necessary has to be > in > > any sysusers table) > > > > also, what's the difference between isntname and isntuser? why for some > > accouts, the values are different? e.g. isntname = 1 but isntuser =0 > > > > thank you. > > > > > > "===steve pdx===" <lins@nospam_portptld.com> wrote in message > > news:eSjJG3ifEHA.1972@TK2MSFTNGP09.phx.gbl... > > > background: sql2k on nt5. > > > > > > there is a view in master database, and a sysusers table in each > database. > > > if an account is found in sysusers table, but not in syslogins table, > what > > > does that mean? > > > how did that happen, > > > and how to clean it up or sync up? > > > > > > thank you. > > > > > > > > > > > > > >
- Next message: Woody Splawn: "Re: Query question"
- Previous message: Andre: "Tracing A Restore"
- In reply to: ===steve pdx===: "Re: question about syslogins and sysusers..."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|