Not sure I'm repeating this , if you have jobs that use sql credentials to backup make sure you change them- I use a combo of batch files and sql to backup, here is an example
SQLCMD.EXE -S server_name -U new_user -P new_password -i D:\sqlscripts\friday7day.sql > From: [email protected] > To: [email protected] > Subject: [NTSysADM] RE: SQL Server and SQL Server Agent account change > Date: Mon, 16 Nov 2015 21:34:37 +0000 > > The one thing that I've run into that's a bit iffy is backups. If you are > doing backups with SQL server (i.e., an agent-based job) you'll need to give > the domain account access to the destination of the backups. > > Of course, this is exactly what Brian said, just a specific example. > > -----Original Message----- > From: [email protected] [mailto:[email protected]] > On Behalf Of Brian Desmond > Sent: Monday, November 16, 2015 4:30 PM > To: [email protected] > Subject: [NTSysADM] RE: SQL Server and SQL Server Agent account change > > That sounds like everything. If you have SQL Agent jobs touching things > external to SQL, you're going to need to update ACLs, etc. > > Thanks, > Brian Desmond > > (w) 312.625.1438 | (c) 312.731.3132 > > -----Original Message----- > From: [email protected] [mailto:[email protected]] > On Behalf Of Jesse Rink > Sent: Monday, November 16, 2015 4:06 PM > To: '[email protected]' <[email protected]> > Subject: [NTSysADM] SQL Server and SQL Server Agent account change > > Wondering if anyone on the list has gone through this. > > I have two SQL 2008 R2 servers, let's call them SQL 1 and SQL2, both running > on Windows Server 2008 R2 virtual machines. > > Both server have the "SQL Server (instance name)" and "SQL Server Agent > (instance name)" services running under the domain\administrator user > account. I'd like to change this so my SQL services aren't tied to my main > domain admin account. > > According to what I've read, all I would need to do is create a new domain > user account without any special privileges (let's call it "SQLService1"), > set a password, and then go to the SQL Server Configuration Manager (SSCM) > tool on SQL1 and SQL2, and adjust the properties of "SQL Server (instance > name)" and "SQL Server Agent (instance name)" services to reflect it using > domain\SQLService1 account instead of domain\administrator. Restart the > services and viola. At that point, SQL should take care of all permissions > and such necessary, etc. > > Anyone done this before? Seems to work well? Anything I'm missing? > > JR > > > > >
