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

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." <billmiami2 [at] netscape.net> wrote in message
news:c57e421f-d696-4625-baea-94011012cfda [at] e39g2000hsf.google groups.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

Thanks, Dan.

Bill E.