Tell me more ×
Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

I have an SQL Server 2012 instance running as a service on my computer, and according to the service page it logs on as account "NT Service\MSSQLSERVER". However I can't see that account name anywhere else including in the "Local Users and Groups" area in the computer management screen, because, as a link below says, that's not a User Account, it's a service name, in that box that Microsoft so helpfully labelled "account". At this point I can see many people being confused.

The task I'm trying to accomplish is to restore files using the SSMS dialog "Locate Backup File", which uses a dialog completely unlike any of the standard windows file open dialogs, probably because it's doing a "remote" job and operating from the security context of the SQL server, another rich source of end user confusion, that I hope this question might help clear up.

So far if I want to restore a backup .mdf/.bak file that I have in one of my folders, I have to set that folder to readable by Everyone or else I can't get in there with the SQL Server "Locate Backup File" window. I find this idea that you're using a GUI talking to a service that has different user accounts and rights than you, that nobody at Microsoft even cared to make clear to you, very confusing even when I have years of experience with windows system administration.

I'm hoping I missed some documentation pages for SQL Server that would tell you, after installing a new SQL server instance, how you might set up security.

Forum posts like this one have even Microsoft staffers saying "this is complicated", and that it "changed, again" in Denali. How does this work now in SQL Server 2012, and how might I add permission to read files belonging to Users to the SQL Database engine's security SID.

share|improve this question
The reason that SQL doesn't use the standard dialog is so you can't pick a file that SQL can't read from. As to how to configure security, are you open to changing the account that SQL runs under or do you want to leave it the way that it is now? If changing the service account is okay then this is easy to take care of. We use named accounts so I can't do testing with the generic MSSQLSERVER account to help with that. – cfradenburg Dec 18 '12 at 17:09
See here: dba.stackexchange.com/questions/23864/… – Jon Seigel Dec 18 '12 at 18:01
If everybody changes their SQL Servers to run with a regular user ID when doing development, that might be the "best practice". I'm just wondering if that's a good idea or not. If manually adding "NT Service\MSSQLSERVER" to the folders I need to add to is the standard idea, I guess that would be the most logical minimal fix, right? Wot I wish is that the SQL server SSMS UI was a little easier to connect to this hidden "NT Server\xxx" account id. – Warren P Dec 18 '12 at 18:50

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.