Re: Advice requested : Storing SID String in SQL table
- From: "Russell Mangel" <russell@xxxxxxxxx>
- Date: Sat, 19 Aug 2006 07:51:16 -0700
"Joe Kaplan (MVP - ADSI)" <joseph.e.kaplan@xxxxxxxxxxxxxxxxxxxxxxxx> wrote
in message news:%231cYWtmwGHA.1624@xxxxxxxxxxxxxxxxxxxxxxx
Another potential option to consider might be to store the user's AD GUID
(assuming you are talking about AD users and groups here). That fits
nicely into a normal SQL unique ID column and is always 16 bytes. You'd
then need to look up the SIDs if you need them from the directory.
Joe K.
Thanks, I also found this information in your
excellant book. (2006 Directory Services Programming).
FYI
I really like the System.DirectoryServices.Protocols
for LDAP access the best. I use LDAP access to get
as much information as I can for Exchange mailboxes,
before I use MAPI 1.0 for mailbox archiving.
Russell Mangel
.
- Follow-Ups:
- Re: Advice requested : Storing SID String in SQL table
- From: Joe Kaplan \(MVP - ADSI\)
- Re: Advice requested : Storing SID String in SQL table
- References:
- Advice requested : Storing SID String in SQL table
- From: Russell Mangel
- Re: Advice requested : Storing SID String in SQL table
- From: Joe Kaplan \(MVP - ADSI\)
- Advice requested : Storing SID String in SQL table
- Prev by Date: Re: Advice requested : Storing SID String in SQL table
- Next by Date: Re: Advice requested : Storing SID String in SQL table
- Previous by thread: Re: Advice requested : Storing SID String in SQL table
- Next by thread: Re: Advice requested : Storing SID String in SQL table
- Index(es):