Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Change SQL Service User Password

Status
Not open for further replies.

clapag22

Programmer
Mar 9, 2001
239
US
I am doing work for a client who uses SQL Server 2000. I told them I need to log into the server as the Windows user the SQL Service is running as so that I can set up some drive mappings and such that they need the server to have. However, they informed me they lost the password and have no idea what it might be. Even spending an hour guessing brought them no closer to the password.

I've never had to change the password for the SQL Service User and if I have them do this I want to make sure there isn't anything special or out of the ordinary that needs to happen. Do I just have them change the password, and then in Enterprise Manager... right click on the server, go to Properties and then go to the security tab and change the password to the new one there? Then do the same thing for the SQL Agent?

It just seems all too straightforward for me.

What am I missing?

Thanks!
Craig
 
You can change the password right from the services console as well. But before you do you should make sure that no other SQL Servers are using that account as well.

- Paul
10qkyfp.gif

- If at first you don't succeed, find out if the loser gets anything.
 
Don't forget to restart the services after you change the password.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)
[noevil]
 
We have multiple servers with SQL Server on them. We have created two service accounts. That way we can change the account/password on one server without affecting others. Let's say all the servers are currently on account1. We change the password on account2 and apply that account to each server as we can. With over 125 servers and over 400 instances, it allows us to make the change and reboot (or restart services) based on business requirements. It also allows us to 'rollback' the account if any unforeseen problems show up.

-SQLBill

Posting advice: FAQ481-4875
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top