|
|
Posted by Hugo Kornelis on 09/29/69 11:52
On 10 Jul 2006 12:32:46 -0700, Justin wrote:
>I am running a SQL maintenance job on a 40 GB database which performs
>optimizations by re-orginizing data and indexes pages. After the job
>is finished, a separate job peforming a SQL transaction log backup is
>run on the same database, which produces a 30 GB transaction log backup
>file. Is there any way to turn off logging during the maintenance
>plan, so that when the transaction log backup occurrs it will not
>produce a large backup file?
Hi Justin,
You can't turn off logging completely, but you can tell SQL Server to
overwrite parts of the transaction log that are not needed for restore
or repair in case of emergency. You do this by setting the recovery
model to simple.
BEWARE: By setting the recovery model to simple, you forfeit the ability
to restore your database to a point in time. To minimize potential for
data loss, you should switch back to full recovery and take a full
database backup (in that order!!) as soon as the maintenance job is
done.
--
Hugo Kornelis, SQL Server MVP
Navigation:
[Reply to this message]
|