{"id":451,"date":"2018-08-20T13:15:01","date_gmt":"2018-08-20T13:15:01","guid":{"rendered":"https:\/\/www.pcvita.com\/blog\/?p=451"},"modified":"2021-12-18T10:20:07","modified_gmt":"2021-12-18T04:50:07","slug":"fix-sql-server-error-1813","status":"publish","type":"post","link":"https:\/\/www.pcvita.com\/blog\/fix-sql-server-error-1813.html","title":{"rendered":"SQL Attach Database Error 1813: How to Get Rid of This"},"content":{"rendered":"
\n

\u201cI attached log file to the SQL Server and I received an error message saying \u201cSQL Attach Database Error 1813\u201d I do not know why it is showing SQL Server error 1813. The database seems fine to me but showing this error. Please tell me solution to get rid of this error message.\u201d<\/i><\/p>\n<\/div>\n

If you are looking for a solution to solve SQL Server error 1813, this is the perfect place. In this write-up, we will share workarounds that can be used to fix SQL Server Error 1813 Attach Database<\/p>\n

First, let us learn what could be the possible reason for getting the SQL error message 1813.<\/p>\n

SQL Attach Database Error 1813 \u2013 Cause<\/h2>\n

The reason for this error is simple and straightforward. If a user attempts to attach any corrupt database file to new SQL Server, they will get SQL Server error 1813. In order to know its remedial method, go to the next section.<\/p>\n

SQL Server Error 1813 Attach Database \u2013 Quick way to Fix<\/h2>\n

Since the error is occurring due to the damaged log files of SQL database, the option we have is to rebuild the database. Then it will become corruption-free and operational. Here is the manual technique to fix SQL Server Error 1813 Attach Database<\/p>\n

Caution:<\/strong> This process is quite long and users need to perform each and every step attentively to achieve the desired result.<\/p>\n

Manual Process of Fixing SQL Server Error 1813<\/b><\/p>\n

    \n
  1. \n
      \n
    1. First, create a new database. This database must have the same name as the one you want to fix. Also make sure that names of MDF and LDF files stay similar to the earlier ones.<\/li>\n
    2. Close any running instances of SQL Server.<\/li>\n
    3. Now, you have to move the original SQL MDF file to the new location and replace the newly created MDF file.<\/li>\n
    4. Delete the LDF file from the new SQL database.<\/li>\n
    5. Now start SQL Server and You will notice that the database will be notified as marked as Suspect.<\/li>\n
    6. Run these commands to make sure you will be allowed to upgrade values in the System tables of Master database.<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n
      USE MASTER\r\nGO\r\nsp_CONFIGURE \u2018allow updates\u2019, 1\r\nRECONFIGURE WITH OVERRIDE\r\nGO<\/code><\/pre>\n
        \n
      1. Set Emergency mode for the SQL Server.\n