I recently changed the sa password on a SQL 2005 std sp3 default instance. I now see .Net SQL data provider connecting with sa login from an app server. From a trace I see:
Application name: .Net Sql Client data provider
HostName: app server name
LoginSID: SID for sa
Sqluser is a sql server logon that is not sa. SSD\sqluser is local admin on app server and is not sa on SQL SERVER and is not in builtin/administrators either. I thought an existing session may explain it but both the app server and sql server
have been restarted since the sa p/w change. Could I be misinterpreting the Profiler output? Any ideas?
View Complete Post