DBCC SHRINKFILE Fails to Shrink Log File in SQL Server 2005

Does your database becomes bulgy? Does it hangs or sometimes take quite longer time to display the fetched query? Searching for an effective way to get rid of the situation? Well, then you don’t have to be worried! You can easily be able to get rid of the situations.

Inspite of the popularity and effectiveness of SQL Server, the database might fails to respond properly. Many a times, user’s might have to face some sort of inconvenience while working with their existing database. The problem generally arises due to oversized MDF files. Continuous storage of data files, increases the size of SQL database and in due course of time it affects the performance of database. It might results in corruption and causes system crash. Sometimes, it also gives rise to serious data loss problems. So, to prevent data loss and other issues of SQL server, it is advised to shrink log file.

How to Shrink DQL Database Log File?

Most of the time SQL users try to truncate the file manually by using SQL server tools like DBCC SHRINKFILE or SQL Server Enterprise Manager under full recovery model in SQL server 2005. Shrinking through this tool is quite easy and faster in 2005 than earlier versions so people prefer it. It is possible that due to some adverse reasons the tool fails to perform the shrink operation and you are unable to truncate the file. Most probably the issue arises due to corruption in database. Under such circumstances you need third party software to repair the corruption and to fix the issue.

Error Message That Appears When DBCC SHRINKFILE Fails

You might have experienced below error message when you try to shrink log file using DBCC SHRINKFILE.

“Server: Msg 8908, Level 22, State 6, Line 1 Table error: Database ID 7, object ID 8, index ID 0. Chain linkage mismatch. (1:679928)->next = (1:679929), but (1:679929)->prev = (1:679930).”

Free Download

Once, the error appears you are unable to reduce the file size as the process gets terminated and your database becomes inaccessible. So, to sort out the problem and gain access over the data you have to find the root cause of the error. The major reasons responsible for the interruption of truncation process and the occurrence of error are mentioned below:

  • DBCC SHRINKFILE unable to delete any page from master database file or sysfile1 system table.
  • Presence of faulty file system.

Automatic Way to Fix the Problem?

In order to resolve database problem, user should have to make use of MS SQL Database Repair software. No matter what ever be the reasons, using this very software one can easily be able to resolve the problem. Apart from better recovery option, the tool is also available with latest GUI interface which makes the recovery console even more easier. So, friends don’t wait until its too late. Just go for it and make your SQL database accessible again.

Free Download