I have a problem with Windows authentication on a SQL server.
The problem occurs when in my company, a woman marries and changes her last name (our Windows logins are based on our last name)!
Indeed, in these cases, the infrastructure service (in charge of our Active Directory) renames the Windows login and not creates a new one.
The problem is that SQL side, when the user logs in and I do a SQL trace (or with the SUSER_SNAME() function), SQL still sees the old login "domain\old_login" and not the new "domainew_login" while on another server everything is ok!
The infrastructure service told me that all AD are synchronized.
So I would like to know what could be the problem :
- how authentication takes place?
- Is that SQL maintains a "cash"?
- Is it Windows that sends the login to SQL or is it SQL which queries Windows?
- If it's Windows, that it send the login or the SID?
- If it's a SID, how SQL find the login?
- If it's a problem of synchronization of the server with the ad, how to force sync?
Thank you in advance.