I am running SQL Server 2012 Enterprise Edition. I have downloaded the AdventureWorks 2012 OLTP data files (both .mdf and .ldf). I saved them to the AW folder that I created in My Documents where I unzipped the file. I go to SQL Server Management Studio (SSMS) right-click on database, and click attach in the context menu. In the dialog I click find.
The UI does not allow me to navigate to folder. I try typing the full path to the file, and then I get the following error:
Cannot access the specified path or file on the server. Verify that you have the necessary security privileges and that the path or file exists.
I closed SSMS and restarted it, this time running as the administrator. Same bad result.
This should not be this hard. What are the exact steps to successfully attach the AdventureWorks2012 database to SSMS?
Thanks!
Put your files to default location for Database Engine data files. If you didn't reconfigure anything it should be
\Program Files\Microsoft SQL Server\MSSQL11.<InstanceID>\MSSQL\Data
And then Attach db using SSMS.
Connecting to the server by Windows Authentication worked for me. I don't know if that is possible in your case.
As Rogitel says about, this could be related to how you have logged in to SSMS itself, rather than the privilege level of the application.
It seems as though, if your user does not have the "sysadmin" role, then they will not have sufficient access to the filesystem on the machine in order to open the file browser.
Setting aside the security concerns for one moment....
In order to grant this role;
- Log in to SSMS using Windows Authentication
- Navigate to Security->Logins
- Either double Click, or Right Click and select Properties on the user you're interested in .
- In the "Select a page" box, select "Server Roles"
- Make sure that the "sysadmin" role is selected
- Press Ok to save the change and close the dialog
- Exit SSMS
- Reopen SSMS and login as the User you wanted, and you should now have sufficient Privileges to browse.
It doesn't matter what permissions the account that you open the management studio has, the important account is the one that the sql server service is running as. By default it only has access to the default location specified during the install, so you can either do as the previous poster said and move your files to there, or add the service account to the permissions of the folder where you want to store your files so that it can access that location.
In my case it was related to the drives not being dependencies of the SQL Server role (Clustered Server). When I added the disks as dependencies under the SQL Server role, I could browse the drives from SSMS again.
Connecting to the SQL server using the 'sa' user did the trick for me.
Not everyone can have permission to do that so make sure the user you are using for SQL Authentication has all necessary privileges.
Just go to service in your computer
and search for MSSQLSERVER restart the service by stop and start.
