March 21, 2011 at 1:37 am
Dear All,
1) If I have performed index rebuilding on one table in logshipped database/Primary database, will it effect the same to secondary database or do we need to again index rebuilding on secondary database or no need?
2)how much down time required if we want to configure logshipping on production?
Please advise.
Thanks and Regards,
Ravi.
March 21, 2011 at 2:19 am
1) If I have performed index rebuilding on one table in logshipped database/Primary database, will it effect the same to secondary database or do we need to again index rebuilding on secondary database or no need?
yes it will and depend on how frequently your database is getting refreshed on secondary.
2)how much down time required if we want to configure logshipping on production?
Again depends on the size of database. But you can avoid most of the time by completing pre-configuration checks like:-
1) network share is ready and sql account have permission to move file.
2) restore the full backup on secondary with norecovery or standby option.
3) The relevant jobs are ready on primary and secondary and test them they are working.
4) Enough space on network share to hold set of backup files and have good network speed.
I think by validating these pre-configuration checks, your log shipping should not take more than 20 min( as only activity required after checks is restore log on secondary and verify it worked.)
----------
Ashish
March 21, 2011 at 2:25 am
Thanks Ashish.
1) If I have performed index rebuilding on one table in logshipped database/Primary database, will it effect the same to secondary database or do we need to again index rebuilding on secondary database or no need?
yes it will and depend on how frequently your database is getting refreshed on secondary.
You mean, no need to perform again index rebuilding on secondary if it was already taken place on Primary database ..right? or we need to do again on secondary.
Please clarify me.
Thanks and Regards,
Ravi.
March 21, 2011 at 2:31 am
how will you able to run the rebuild on logshipped database?
your database will be either in standby/read-only mode or restoring mode.
----------
Ashish
March 21, 2011 at 2:32 am
ravisamigo (3/21/2011)
Dear All,1) If I have performed index rebuilding on one table in logshipped database/Primary database, will it effect the same to secondary database or do we need to again index rebuilding on secondary database or no need?
2)how much down time required if we want to configure logshipping on production?
Please advise.
Thanks and Regards,
Ravi.
1) If I have performed index rebuilding on one table in logshipped database/Primary database, will it effect the same to secondary database or do we need to again index rebuilding on secondary database or no need?
If you perform an index rebuild on the primary then when the log backup that contains the index rebuild is shipped and subsequently restored to the secondary then the refresh will be applied to the secondary
2)how much down time required if we want to configure logshipping on production?
Aa far as I can remember and assuming that your production database is going to be the primary database in the log ship, there will be no downtime for the production database.
Gethyn Elliswww.gethynellis.com
March 22, 2011 at 2:06 am
Slight warning here: performing an index rebuild could result in a very large transaction log backup, which in turn could knock your log shipping temporarily out of sync (depending how fast the connection between the two database servers is).
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply