Optimization problem

Hi,
I got a problem when run optimization. In SQL 7, transaction log usage is
very limit but after upgraded to SQL 2000, found the optimization job ate 9G
transaction (the db size is 21G). How can I limit the transaction log usage?
Thanks & regards,
henryHi,
you can set maximum size of the log. But then set an alert to notify you
when log is nearly full.
Other good way to keep tran log small is to regulary backup it...
Danijel
"Monster Henry" <henry@.monster.com> wrote in message
news:eJnzn3cAFHA.3592@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I got a problem when run optimization. In SQL 7, transaction log usage is
> very limit but after upgraded to SQL 2000, found the optimization job ate
> 9G transaction (the db size is 21G). How can I limit the transaction log
> usage?
> Thanks & regards,
> henry
>|||Hi
The transaction log growing due to a Index Re-Builds are expected. Since the
operation is fully logged, you need as much space (1.2 times) as the biggest
table when a clustered index is re-built.
Regards
Mike
"Monster Henry" wrote:

> Hi,
> I got a problem when run optimization. In SQL 7, transaction log usage is
> very limit but after upgraded to SQL 2000, found the optimization job ate
9G
> transaction (the db size is 21G). How can I limit the transaction log usag
e?
> Thanks & regards,
> henry
>
>