By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
455,379 Members | 1,377 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 455,379 IT Pros & Developers. It's quick & easy.

SQL 2005: Renamed 'sa' account

P: n/a
We have renamed the 'sa' account on a SQL Server 2005 machine. When
we run

SELECT * FROM syslogins

it appears that 'sa' no longer exists as a valid SQL login. However,
when we look at running processes through sp_who, we see that 'sa' is
still being used in various background operations, even when we shut
down and restart the SQL Server. Can someone explain this?

Bill E.
Hollywood, FL
Apr 7 '08 #1
Share this Question
Share on Google+
2 Replies


P: n/a
My guess is that the reported login name for these internal system processes
is hard-coded as 'sa'. I think this is a bug and will report it on via
Connect feedback (http://connect.microsoft.com/SQLServer) if not already
filed.

--
Hope this helps.

Dan Guzman
SQL Server MVP
http://weblogs.sqlteam.com/dang/

"Bill E." <bi********@netscape.netwrote in message
news:c5**********************************@e39g2000 hsf.googlegroups.com...
We have renamed the 'sa' account on a SQL Server 2005 machine. When
we run

SELECT * FROM syslogins

it appears that 'sa' no longer exists as a valid SQL login. However,
when we look at running processes through sp_who, we see that 'sa' is
still being used in various background operations, even when we shut
down and restart the SQL Server. Can someone explain this?

Bill E.
Hollywood, FL
Apr 9 '08 #2

P: n/a
Thanks, Dan.

Bill E.

Apr 10 '08 #3

This discussion thread is closed

Replies have been disabled for this discussion.