I have seen some strange behaviour where a connection flips from the login it connected with to use "sa".
I have evidence of this captured in a .trc file, where you can see a particular SPID being used (via Management Studio) under a windows login, then for some reason the login name changes to "sa" for a couple of queries, then changes back to the windows login.
Has anyone else noticed behaviour like this? It's starting to cause me real hassle as it shows up on our Audit reports, when we're only supposed to use "sa" in emergencies only.
Could you please file a defect report for this on the Connect site (http://connect.microsoft.com/sqlserver)? Defects reported by customers on the Connect site go directly into our internal defect tracking system so we don't lose any information. Also, customer reported issues have additional weight with the development team when we are prioritizing future work.
If possible, try to come up with a compact set up steps that illustrate the issue on a sample database such as AdventureWorks or Northwind. That will make it much easier for us to figure out what is going on. Attaching a .trc file might help as well if the problem queries are coming from a dialog or other UI (other than the query editor).
Thanks,
Steve
Have you disabled SA account on your server?
What are privileges for the SQL Server services account?
No comments:
Post a Comment