January 20, 2010 at 8:45 am
Hello
I have to do a dbreindex soon on a database that is being logshipped. The database is large and to restart logshipping is not really an option.
Having tested some of the tables, it can take 4 hours and produce 40-50gb of transaction logs for one table.
My question is: Has anyone ever come across a situation where log shipping could not handle the dbreindex? Or does anyone know that this will not work?
I know the index gets written to the logs but do not know what the restore on the secondary server will make of it.
SQL2000 on windows 2003.
Thank you
William
January 20, 2010 at 8:50 am
Its been a while since I’ve worked with log shipping, but as far as I remember, it simply does the reindex operation on the secondary database just like it was done on the primary database.
Adi
--------------------------------------------------------------
To know how to ask questions and increase the chances of getting asnwers:
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
January 20, 2010 at 8:55 am
Thank you - I am sure that is what it will try to do - I am just worried when the reindex is contained in numerous logfiles over a two hour period (every 10 minutes) and the secondary server is trying to restore each one as it comes in.
Hoping it will cope!
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply