verify account that SQL is running in

[ChrisR]

Archived from groups: microsoft.public.sqlserver.server,microsoft.public.win2000.general (More info?)

I have a domain admin account that several (but not all) of my SQL boxes run
in. I need to change the password on this account and got to thinking about
a possible gotcha I want to avoid.

1; Joe User decides that SQL should run in a different account altogether.
(Not merely a password change.) He changes the account in the Services
screen. Before he has a chance to restart the Service for the new settings
to take affect, he has a heart attack/ goes to pee/ gets a phone call with a
job offer for twice what he's currently making. The point is that Joe User
then never restarts the service.
2; ChrisR the DBA decides 10 minutes later that the account that SQL is
currently running in should have it's password changed. But he logs onto the
box Joe User just logged off of, and visually sees that the Services aren't
running in the account thats getting a password change, (don't forget Joe
User changed the account, but never restarted the services) so he doesn't
worry about it. ChrisR the DBA doesn't include this box on his list of
affected servers..... until all the applicattions blow up once the password
changes.


Is there a way to really know what account my SQL boxes are running in? I
know this scenario is unlikely, but it is possible.

TIA, ChrisR

 

[Guest]

Archived from groups: microsoft.public.win2000.general,microsoft.public.sqlserver.server (More info?)

http://www.microsoft.com/technet/scriptcenter/guide/sas_ser_oeje.mspx
Sample goes here: http://www.serverwatch.com/tutorials/article.php/1576131

Let me know if that worked for you.
--
HTH, Jens Suessmeyer.

---
http://www.sqlserver2005.de
---


"ChrisR" wrote:

> I have a domain admin account that several (but not all) of my SQL boxes run
> in. I need to change the password on this account and got to thinking about
> a possible gotcha I want to avoid.
>
> 1; Joe User decides that SQL should run in a different account altogether.
> (Not merely a password change.) He changes the account in the Services
> screen. Before he has a chance to restart the Service for the new settings
> to take affect, he has a heart attack/ goes to pee/ gets a phone call with a
> job offer for twice what he's currently making. The point is that Joe User
> then never restarts the service.
> 2; ChrisR the DBA decides 10 minutes later that the account that SQL is
> currently running in should have it's password changed. But he logs onto the
> box Joe User just logged off of, and visually sees that the Services aren't
> running in the account thats getting a password change, (don't forget Joe
> User changed the account, but never restarted the services) so he doesn't
> worry about it. ChrisR the DBA doesn't include this box on his list of
> affected servers..... until all the applicattions blow up once the password
> changes.
>
>
> Is there a way to really know what account my SQL boxes are running in? I
> know this scenario is unlikely, but it is possible.
>
> TIA, ChrisR
>
>
>