Can .ldf Files Be Repaired

repair corrupt mdf and ldf files

The importance of having a stiff database management system is very much compulsory for personal and professional usage. It not only helps to manage official piece of work just helps in keeping track of administrative record too. There can be so many reasons backside the corruption of the database that results to finally loss of your important information. Many time it is also seen that while MDF file is get corrupted, DB admin shows the error when tries to execute DBCC CHECKDB control. It will likewise shows error when admin tries to restore files from an upgrade fill-in.

This DBCC CHECKDB is mainly used to repair corrupt MDF files. It perfectly recovers the MDF files that got damaged due to some logical abuse. The admin restore data from the updated backup as when required. Principal issue arises when no database backup is available using which it tin can be restored once again.

sql-dbcc-checkdb

You may get stuck with the following error

Error 5101: DEVICE ACTIVATION ERROR

This fault mostly comes when the physical file proper noun 'C:\%path to db%\db_log.LDF ' plant incorrect. When it is corrected yous might get the mistake, "db Adhere failed".

LDF is the log file that comes attached with MDF database files. It is the most mutual fault which Admin gets when they endeavour to open their MDF files in guild to access the Database objects. To fix this error, admin runs DBCC CHECKDB ('dbname', REPAIR_REBUILD) control. However, while executing this command admin gets another mistake that is mentioned below

screen2

Server: Msg 945, Level 14, State 2, Line ane

Database can't be opened due to inaccessible files, disk infinite or insufficient retentiveness. Run into the SQL server fault log for further more details about this.

1307_proble1 (1)

Steps for recovery when LDF is corrupted

First employ sp_attach_single_file_db

CODE

USE master;GOEXEC sp_detach_db @dbname = 'AdventureWorks';EXEC sp_attach_single_file_db @dbname = 'AdventureWorks', @physname = Northward'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Information\AdventureWorks_Data.mdf';

If this won't work endeavor the following steps:

one) proceed a re-create of your.MDF file

2) create a new database called( default file location.

3) end using SQL Service

4) Delete the fake_Data.MDF and copy your.MDF to where fake_Data.MDF is actually saved and rename the file with the same name of fake_Data.MDF

v) now Kickoff SQL Service

6) your fake database will appear every bit suspect in EM.

seven) Open up Query Analyzer and execute the post-obit code in the Main database:

Code

sp_configure 'permit updates',i become reconfigure with override go update sysdatabases set status=-32768 where dbid=DB_ID('fake') go sp_configure 'allow updates',0 go reconfigure with override get

This volition accept your database in the emergency recovery mode

eight) Once again Stop SQL Service

9) Delete the fake_Log.LDF file

ten) And then restart the SQL Service

11) In Query Analyzer run the following (with correct path for log)

Lawmaking

dbcc rebuild_log('fake','h:\fake_log.ldf') become dbcc checkdb('fake') — to check for errors become

12) now, rename the files, run the following code in Query Analyzer. This time yous are really accessing the database and then that you can use DTS or BCP to motility the data to another databaseCODE

utilise master become sp_helpdb 'faux' go /* Brand a note of the names of the files , yous will need them in the next bit of the script to replace datafilename and logfilename – information technology might be that they accept the correct names */ sp_renamedb 'fake','your' go alter database your Modify FILE(NAME='datafilename', NEWNAME = 'your_data') become alter database PowerDVD301 MODIFY FILE(Proper noun='logfilename', NEWNAME = 'your_Log') go dbcc checkdb('your') become sp_dboption 'your','dbo utilise merely','simulated' become utilize your go sp_updatestats become

13) you should now have a working database. However the log file size is too small so unfortunately your files will exist called fake_Data.MDF and fake_Log.LDF but you can solve this issue past detaching the database properly and and so renaming the files and reattaching it again.

14) Run the following lawmaking in QA

Lawmaking

sp_detach_db your –now rename the files then reattach sp_attach_db 'your','your.mdf','your.ldf'

These are the few errors that come and disturb y'all at your work which finally results to losing lots of information. So to prepare it y'all can try the higher up mentioned solution simply if in instance using these steps you lot are not able to prepare your corrupt .mdf and .ldf file then you lot must try a trusted third party repair tool to set up out this corruption issue. It's improve to repair your decadent SQL .mdf and .ldf files using SQL Repair Tool as it is the most reliable tool for recovering damaged SQL files. Efficient in repairing MDF and LDF files, and recovers views, indexes, tables, stored procedures, unique/primary keys etc. that is saved in your damaged SQL database.

STEPS TO Gear up CORRUPT SQL DATABASE:

Step ane: Stop running MS SQL server, the repair process is done on the re-create of decadent database and then tap to 'OK' button and continue.

Step two: at present click on the 'Select database' push and select the path of decadent MDF file. Afterward that search for your corrupt database file by using 'Look in' and 'File Type' push button. To outset with the repairing procedure click on the 'Browse file' button.

MS SQL

Step 3: The consummate listing of recoverable objects of database is in tree view on the left side of the window. Tapping to the object you can run across the preview. MS SQL

Step 4: Click on the 'Start Repair' icon to begin the process. To salve the repaired file in the desired location click on the browse button and assign the path, otherwise the repaired file will be saved in the 'Default SQL Location'. Click on the 'Ok' button. MS SQL

Jacob Martin is a technology enthusiast having experience of more than iv years with great involvement in database assistants. He is expertise in related subjects like SQL database, Access, Oracle & others. Jacob has Master of Science (M.Southward) degree from the University of Dallas. He loves to write and provide solutions to people on database repair. Apart from this, he likewise loves to visit different countries in free time.