![]() | |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
We usae Sql2000. I'm setting up backups jobs and need advise. When I run a backup of a database, does it automatically clean out the transaction log ? For a complete backup ? for a differential backup ? |
|
When would it be best to run a shrinkdatabase command ? Why would I want to run the shrinkdatabase ? |
#3
| |||
| |||
|
|
David Greenberg (davidgr (AT) iba (DOT) org.il) writes: We usae Sql2000. I'm setting up backups jobs and need advise. When I run a backup of a database, does it automatically clean out the transaction log ? For a complete backup ? for a differential backup ? No. Backing up the database and backing up the transaction log are two separate operations. Before you go ahead, determine what level of recovery you need. If the database goes belly-up, do you need restore to a point in time? Or would you be content with restoring the most recent backup? In the former case, you need to use full recovery and you need to back up your transaction log regularly. In the latter case, you can go with simple recovery and forget all about the transaction log. SQL Server will automatically truncate the transaction log regularly so that only active transctions remain. When would it be best to run a shrinkdatabase command ? Why would I want to run the shrinkdatabase ? Most of the time you don't want to. Shrinking the database is a very exceptional operation. This article gives some insight about this: http://www.karaszi.com/SQLServer/info_dont_shrink.asp So when does SqlServer decide to shrink the database automaticaly ? When |
#4
| |||
| |||
|
|
So when does SqlServer decide to shrink the database automaticaly ? When a backup is performed ? |
![]() |
| Thread Tools | |
| Display Modes | |
| |