Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
scottpt
Posting Yak Master
186 Posts |
 Posted - 2005-03-01 : 10:22:54
|
| I insert directly into the sysxlogins table. I change the name from Server1\wingroup to Server2\wingroup before doing the insert. Everything looks good, but no one can log in. Also, when you grant access on Server two sysusers has a completely different SID the syslogons. SysxloginsServer2\wingroup 0x010500000000000515000000FD43461EFA4F0C2F43170A32EC030000Ran sp_adduser 'Server2\wingroup','wingroup','db_datareader' this is what showed up in sysuserswingroup 0x0105000000000005150000002FD5EC6D1ADE2C7A828BA628657F0100Has anybody delt with this before? |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2005-03-01 : 13:20:56
|
quote:
Originally posted by scottpt
I insert directly into the sysxlogins table.
You are joking, right? Please tell me that you are joking. If you aren't, this is a really, really, really, really bad idea. You should never add data into the system tables without going through the appropriate MS supplied stored procedures. So why can't you just use sp_grantlogin to add a Windows account? To keep SIDs in synch, use sp_help_revlogin which you can find a copy of in the forums here or by googling it.Tara |
 |
|
|
|
|
|
Copied Win Auth Logins not working