Error 5123 Attach Database
Contents |
More > Database Administration Problem When you attach a database in SQL Server 2008R2 which was detached by a user with a different login you may get this error: CREATE FILE encountered operating system error 5(Access is denied.) while attempting to open or create the physical sql server 2005 attach database error 5123 file... (Microsoft SQL Server, Error 5123) This is a screenshot of the error: In this tip microsoft sql server 2008 error 5123 we will cover how this can be resolved. Solution You get this error because two different logins did the detach and attach operations. So the error 5123 unable to attach database files, when detached, were owned by the first login, but the attach failed because the login that was used was not the owner of the mdf and ldf files. When we detach database files, the owner becomes the person who did the
Error 5123 Severity 16 State 1
detach command, so to resolve the issue we need to change or add the other login as the owner of the mdf and ldf files. Find the below steps to resolve this issue. Steps Lets consider that someone detached a database and you have to attach it to bring the database online. For this example, we will use two logins to perform this activity. I will detach the database using the first login and then try to attach it with the second login. Not error 5123 in sql server 2012 that both accounts are part of the local administrator group on the server. Step 1Here I detach the database named "stats1" with my login account. Step 2Now I have logged in with the second account and will try to attach the database, but during this process I am getting the below error. Step 3Right click on the "stats1.mdf" file and select properties to check the permissions of the mdf file. Here we can see that only one account has permission to the "stats1.mdf" file because that was the account that was used to detach the database. Step 4To resolve this issue, click on the Add... button to add the other login or any other login needed and give the login Full Control. You should do this for the "ldf" file as well. Once you have completed this task click the OK button. (Note for other OS versions you may have an Edit option , click this first and then you will see the Add... option.) Step 5Now try the attach again and it should work. The permissions prevented the files from being modified should they reside in a directory that has open permissions. For example, if the permissions are not set and the operating system permissions on the database directory are set to Full Control for everyone any account that has access to that directory can delete or modify the database files even though they may not have SQL Server permissions to modify the database itself. Next Steps If
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss sql server error 5123 create database the workings and policies of this site About Us Learn more about
Sql Error 5123 Access Denied
Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow
Sql Error 5123 Create Database
Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each https://www.mssqltips.com/sqlservertip/2528/database-attach-failure-in-sql-server-2008-r2/ other. Join them; it only takes a minute: Sign up Can't attach any database to SQL Server 2012 up vote 3 down vote favorite 2 Ok this is what I get: Failed to retrieve data for this request. (Microsoft.SqlServer.Management.Sdk.Sfc) Additional information: An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo) CREATE FILE encountered operating system error 5(error http://stackoverflow.com/questions/17553403/cant-attach-any-database-to-sql-server-2012 not found) while attempting to open or create the physical fife 'C: \Program Fifes (x86) \Microsoft SQL Server \MSSQL.1 \MSSQL \Data \MyCompany.mdf. (MIcrosoft SQL Server, Error: 5123) I have already reinstalled SQL Server 2012, and it still doesn't work. Before this problem I tried to attach the AdventureWorks database and insert some command (I have deleted it) and since then I keep having this problem. I am new to SQL Server. Thanks sql sql-server-2012 share|improve this question edited Jul 9 '13 at 18:17 marc_s 452k938641029 asked Jul 9 '13 at 16:23 Lazar Lukic 18115 2 There seem to be some typographical errors in your error-text. The path is missing a number I think. MSSQL11? Please confirm SQLServer version. Also you have "fifes" not "files". –Tim Jul 9 '13 at 16:29 MSSQL.1 that's what it says...And yes fife is a typo. –Lazar Lukic Jul 9 '13 at 16:37 If you open the database in SSMS and look at its properties, what does it say there for the path? –Ti
log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more http://dba.stackexchange.com/questions/82060/error-in-attaching-mdf-file-from-a-crashed-server-to-a-new-server about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Database Administrators Questions Tags Users Badges Unanswered Ask Question _ 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. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a error 5123 question Anybody can answer The best answers are voted up and rise to the top Error in attaching mdf file from a crashed server to a new server up vote 4 down vote favorite 1 One of our server hosting an important database crashed. The sysadmin team could only access the files by erasing the password with a tool and then log in to access the .MDF files. I copied the error 5123 create data to the new server and attempted to attach it, but I get the following error: TITLE: Microsoft SQL Server Management Studio Failed to retrieve data for this request. (Microsoft.SqlServer.Management.Sdk.Sfc) ADDITIONAL INFORMATION: An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo) CREATE FILE encountered operating system error 32 (The process cannot access the file because it is being used by another process.) while attempting to open or create the physical file 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\MSDBData.mdf'. (Microsoft SQL Server, Error: 5123) sql-server share|improve this question edited Nov 9 '14 at 9:08 marc_s 5,41632743 asked Nov 6 '14 at 13:51 kombo 2171411 add a comment| 2 Answers 2 active oldest votes up vote 2 down vote In general if you have a crashed server and need to bring up your databases on a new server you want to restore from backup not copy and reattach the mdf files. The crash could have caused corruption that will not exist in the backup. You can restore your system databases as well although it isn't always recommended. If you are going to you need to make sure your new system is as close to the old as possible. Particularly the patching level for SQL Server. If you do not have backups, and