July 21, 2005 at 4:29 am
I was just running a stored proc that i got from this site called spAuditPasswords on one of our prod servers. It failed due to a subquery returning more than one value. This i found odd so after a bit of testing I've found that there are two identical login names in the sysxlogins table, this login only appears once in syslogins though. The second login in sysxlogins has no SID, has a SRVID of 2 (whereas genuine logins appear to have NULL) and a DBID of 0, which doesn't exist in sysdatabases. I'm not a big fan of updating system tables but i'm interested in why this might have happened and if its wise to remove the row?
Thanks in advance.
Growing old is mandatory, growing up is optional
July 21, 2005 at 4:35 am
Ah, is this to do with linked servers?
Growing old is mandatory, growing up is optional
July 22, 2005 at 4:05 pm
No it is not wise;
Look at your linkservers one of them has a login defined on it.
Tim S
July 22, 2005 at 4:17 pm
He updated his script here
http://www.database-security.info/Tools/SQLServer/spAuditPasswords.txt
Tim S
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply