Truncate Logs on SQL Server 2008


Truncation of Logs in SQL Server 2008 is different from SQL Server 2000/2005. The Truncate_only Option has been terminated (I guess this was to save the integrity of Data). Until Microsoft makes an option to right click on the Database and Select "Truncate Database". Follow the steps below for now.

Do you have a SQL Server 2008 Database with Truncating Logs that are out of control, the Event Viewer is showing Event 9002 MSSQLServer. Then you need to immediately truncate your logs for your database. This will allow you to be able to access, login and use your database. If you are unable to login to vCenter, the first thing you need to do is check your error logs for Event 9002 MSSQLServer and see if you have a message for the database being Full.

1. Verify if you have the following Error under “Application” in Event Viewer on your Windows 2008 Server:
  • Event 9002, MSSQLServer
Event 9002, MSSQLServer



2. After verification, open the SQL Server 2008 Management Studio. Login and select the database. (Need Microsoft SQL Server 2008 Management Studio? - Click Here)

3. You will need to temporarily switch the Database to “Simple” in order to manually truncate the logs. Right-click on your database and select PROPERTIES.
  • Simple DB
Simple DB


4. Select OPTIONS and then Switch the Database to “Simple” and click OK.
  • Options Change for "Simple"
Options Change for "Simple"


5. After you have changed the Database to “Simple”. You can begin your cleanup. Click on the Database and run the following commands (You can highlight the text and click F5 key to run the commands or click on EXECUTE in the toolbar:
SELECT name, size FROM sys.database_files;
GO

6. You will see two lines that tell you the actual name of your database (if it has been changed or is somehow different from a backup, etc. You never know so CHECK FIRST!)

7. After you have the correct log file database name run the following command:
DBCC SHRINKFILE (DATABASE_log, 2);
GO
  • The Truncanatorrrr!
The Truncanatorrrr!


8. After completing the maintenance. Follow Steps 1-4 to Change the Database back to “Full”.
FYI. Make certain that you have Maintenance Plans Setup for Full AND Transaction Log Backups!

9. Immediately Perform a Full Backup of the Database after you have completed all of your operations.

Popular posts from this blog

How to Configure HP ILO 4 for Active Directory Login

How to Configure BGInfo for Windows Server 2012 R2

How to Fix /storage/core filesystem Out of Disk Space Error on VCSA 6.0U1