Reputation
251
Top tag
Next privilege 300 Rep.
Create new tags
Badges
2 13
Impact
~12k people reached

Mar
8
awarded  Popular Question
Mar
2
awarded  Popular Question
Feb
20
awarded  Nice Question
Jan
21
awarded  Commentator
Jan
21
comment Why would suser_name() not reflect an AD account name change?
I can't say for sure this is the issue, but I believe this or something like it is. Rebooting the server (which happened for separate reasons) seems to have cleared it up, at least for this case. It's not clear if it will come up again.
Jan
16
comment Why would suser_name() not reflect an AD account name change?
@KennethFisher For the other user, the GUI/SQL matched the new name, and creating a login for them did resolve the issue. Cool! But why does this fix it?
Jan
15
comment Why would suser_name() not reflect an AD account name change?
@KennethFisher I was able to reach one user and gave this a try. Using the GUI "New Login" menu in SSMS, I searched for and found their new account name. But the SQL generated said `CREATE LOGIN [domain\oldname], which seems noteworthy. suser_name() is still returning their old name as well. I appreciate the suggestion.
Jan
15
comment Why would suser_name() not reflect an AD account name change?
@srutzky It is a default MSSQLSERVER instance running under a domain account. Unfortunately I don't have the password to log in with it. I have not tried suser_sname() as the user yet, I believe that it is the same as suser_name() if given no arguments. It's worth a try though - thanks!
Jan
15
asked Why would suser_name() not reflect an AD account name change?
Nov
26
awarded  Popular Question
Oct
14
awarded  Curious
Oct
13
awarded  Yearling
Aug
6
awarded  Caucus
Feb
4
comment SQL Server Service Broker messages in one database fails unless SA owns the database? What's going on here?
@Rikalous This is an AD environment but I am connected, however the SQL Server instance is running from my workstation if that matters. Did you run into a similar issue?
Feb
3
comment SQL Server Service Broker messages in one database fails unless SA owns the database? What's going on here?
@AaronBertrand I set TRUSTWORTHY on a new copy of the database (same steps as above, except giving sa ownership) and did not observe a difference. I actually don't have a problem with sa owning databases, I just want to understand why that fixes the issue. Finally, it seems I have some reading to do about principles... I had thought that a schema was a principle. Thank you for pointing out that error!
Feb
3
asked SQL Server Service Broker messages in one database fails unless SA owns the database? What's going on here?
May
1
awarded  Notable Question
Apr
22
accepted What are the hazards of upgrading a SQL Server service pack?
Apr
22
revised What are the hazards of upgrading a SQL Server service pack?
Reworded the first line so it wasn't so open-ended
Apr
22
asked What are the hazards of upgrading a SQL Server service pack?