NOTE : The issue is occurring only if windows authentication is used to log in SSMS. SQL Server authentication works just fine. I have tried domain user permission on the database file path and also tried running SQL Server services as domain user, still no luck.
Need help on this.
Hi @NishantKumar-1885,
Please add the Full Control permission for the windows authentication user in the file property.
Please refer to the following link and picture:
SQL Server Operating system error 5: “5(Access is denied.)”
Best Regards,
----------
If the answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hi @Nishant Kumar ,
Unable to open the physical file "\machineRemote\ShareName\sample\sample_database.mdf".
Could you please use the file in local server? Like in C:\ or D:.
Best Regards,
Hi @Nishant Kumar ,
It's better for you to use local folder to store the mdf and ldf file.
Hope the following link will be helpful:
WINDOWS FILE SHARING
Best Regards,
SQL Server database engine service account must have permissions to read/write in the new folder.
To fix it, I did the following:
Added the Administrators Group to the file security permissions with full control for the Data file (S:) and the Log File (T:).
Attached the database and it works fine.
for respective users
Not the user accesses the database file, it's the database engine with it' service account and that service account needs full access.
BTW, hosting a SQL Server database file on a NAS share is not the best idea, one network hick-up and the database may gets corrupt; a SAN or local disks are a better solution.
@Olaf Helper I have checked the service account under which SQL Server is running. I am running it under a domain user and the user has Full control over the file and folders.
Thanks for the suggestion. I understand that is not the best idea but I want to know how can I solve this issue.
The SQL Server service account requires access to the files, not the user running the account.
If you detached the file, the file rights are set to the service account on the server you dethatched the files from. You must reset the rights to be accessible to the "machineRemote" SQL Server service account.