Gurus,
I apologize for spamming the boards with all these questions but it seems like a lot of folks are on at the moment so I am going to post another question.
Okay, we have a target system that is an MS SQL database and needs to have some attestations run. The database admin told me that if a person's user ID changes (say a girl gets married), their actual database account doesn't get changed to reflect the new ID, he just makes an alias that points back. So if Julie Foo (JFoo2) gets married to Danny Bar and her AD account is changed to JBar4, rather than changing the user's account on all the tables she's in, he just makes an alias that tells the database that JBar4 is also JFoo2.
With this kind of issue, if Quest pulls AD records and locates JBar4 and adds her to the Person table, when the attestation case is run, her account in the DB is technically still JFoo2 so it won't find her and thusly won't make an attestation case. We have found that the DB DOES store the user's AD SID but it stores it as a varbinary so JBar4's binary SID may be 0x0040301032 whereas her AD SID is a string like: S-0021354HH1. Can we somehow run a custom process that can read the SID field from the DB and then convert it to the string format that AD will read? If we can do that then we can use the converted AD SID as the FK for Quest on that system.
Soryr if this is a weird question but there are A LOT of smart people here. 