Hi,
We have finished SQL upgrade recently from SQL 7 to SQL2K. One thing that we
have noticed is we used to run DBReindex before on SQL 7 but the log file
stay with in the limit. However, with SQL 2K when we run DBReindex. log file
grow crazy.
Is this normal behavior of DBreindex on SQL2K. Can we turn off logging?
We have Full recovery model configured on SQL 2K.
Another neat way in SQL 2K is to use IndexDefrag. I am afraid though, will
IndexFrag also increase the log file size dramatically.
Also, is there any whie paper that talks about the pros and cons of these
two methods of defraging data in SQL.
Your help is appreciated.
Thanks,
MohHere's a new whitepaper that I helped with that discusses pros and cons of
indexdefrag and dbreindex.
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/sql/maintain/optimize/ss2kidbp.asp
Enjoy!
--
Paul Randal
DBCC Technical Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Moh Abb" <mabbas@.aligntech.com> wrote in message
news:eJqKOI6TDHA.3796@.tk2msftngp13.phx.gbl...
> Hi,
> We have finished SQL upgrade recently from SQL 7 to SQL2K. One thing that
we
> have noticed is we used to run DBReindex before on SQL 7 but the log file
> stay with in the limit. However, with SQL 2K when we run DBReindex. log
file
> grow crazy.
> Is this normal behavior of DBreindex on SQL2K. Can we turn off logging?
> We have Full recovery model configured on SQL 2K.
> Another neat way in SQL 2K is to use IndexDefrag. I am afraid though, will
> IndexFrag also increase the log file size dramatically.
> Also, is there any whie paper that talks about the pros and cons of these
> two methods of defraging data in SQL.
> Your help is appreciated.
> Thanks,
> Moh
>
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment