You might find that the transaction logs on the VirtualCenter Database can get quite large. Backups of a SQL database should purge the system of transaction logs and keep the database in a manageable size. If it does not then review your database backup procedures with your database admin team.
There is another way of shrinking the database and keeping this small. However, this does involve lowering the level of fault-tolerance provided by the transaction logs on a production database. So proceed with caution – the procedure below would certainly be appropriate for a development environment.
You can use SQL Enterprise Admin to backup and shrink these files with:
1. Run SQL Enterprise Manager
2. Right-click on the database
3. Select All Tasks and Backup Database
4. Select Transaction log
Note:
Make a path to a disk somewhere and call it whatever you choose. After that is done, it will take
awhile.
5. Right-click again choose All Tasks and Shrink
Database
6. Click on Shrink Files
7. Change the file name to the log file and shrink it
To stop these transaction logs getting too large you can change the recovery options to Simple using:
1. Run SQL Enterprise Manager
2. Right-click on the database
Requires Free Membership to View
3. Select Properties
4. Select Options, and set the Recovery to “Simple“.
You can force a shrink of the database after a backup through SQL Enterprise Admin Tools – alternatively you might wish to look at Microsoft support document that explains how to automate shrinking the Transaction Log in SQL Server 2000 with DBCC SHRINKFILE.
Link:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;272318
This was first published in January 2006
Join the conversationComment
Share
Comments
Results
Contribute to the conversation