Re: Transaction log and rebuilding indexes
- From: "Abba" <SQL_Help@xxxxxxx>
- Date: Mon, 8 Jun 2009 15:36:38 +0530
Chirag,
I would also make sure that I have a valid FULL backup before I change the
recovery model...
1) Check if the last FULL backup ran successfully
2) Make sure that Log backup is not running currently(else step3 would
error). Stop and disable the job.
3) Change recovery to SIMPLE
4) REBUILD ALL INDEXES using sp_msforeachtable 'ALTER INDEX ALL ON
?REBUILD'
5) Change Recovery to Full
6) Perform full backup
7) Enable Log backup job
hth,
AbbA
"c_shah" <shah.chirag@xxxxxxxxxxx> wrote in message
news:658b6199-b0da-4593-a15c-9caac97fec8e@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I have an *old* SQL 2000 database (SQL2K Standard), size of the
database is around 8 GB
in order to keep transaction log (current file size is 0.5GB) from
exploding, largest table in the db is around 1 GB
I am setting up the following tasks as scheduled job on Sunday at 1 AM
(database will not be going to used most probably at that time)
1) Change recovery to SIMPLE
2) REBUILD ALL INDEXES using sp_msforeachtable 'ALTER INDEX ALL ON ?
REBUILD'
3) Change Recovery to Full
4) Perform full backup
I can do index defrag instead of rebuilding them but
Is this the right way Or just increase the T-log to about 1 GB of
size?
Just to make sure ...?
.
- References:
- Transaction log and rebuilding indexes
- From: c_shah
- Transaction log and rebuilding indexes
- Prev by Date: Re: Problem with multi-currency format number in a textbox, RS2005 sp3
- Next by Date: Re: Collation advice going from 2000 to 2008
- Previous by thread: Re: Transaction log and rebuilding indexes
- Next by thread: Configuring second instance different IP on 1433
- Index(es):
Relevant Pages
|