An employee at a client has just got married and as a result they have changed her details, login name et al., in Active Directory (AD).
The problem is SUSER_NAME() in procedures and the NTUSERNAME in SQL Server Profiler still shows her original maiden name.
All connections by this login are made using Windows Authentication and there aren't any indvidual logins set up in SQL Server, access is granted through the "Everyone" AD group.
Is there some kind of cache in SQL Server or a storage of login name somewhere that I don't know about that might be causing this to happen.
I'm informed by the client's IT team that every possible location in AD has been changed to the new name.