That is.basically correct but u might run into permissions problems.I.file system and.registry if account isnt a local admin on the system. I know during the original installation sql.applies.the correct.registry and.file permissions to.account provides in setup
But.if that account wasnt Lowest privs to start with basically a user.account u might run into security perms oroblems afterwards On Nov 16, 2015 4:06 PM, "Jesse Rink" <[email protected]> wrote: > 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 > >
