August 24, 2006 at 3:08 am
Hi all,
We have two servers running in a log-shipping setup whereby the production server pushes out transaction logs on an hourly basis to the secondary machine which has the databases set up as read-only. The primary database in question is a 200GB, 1015 table ERP database which averages about 140 concurrent user connections and roughly 50-200 transactions per second.
What I want to do is to run a DBCC DBREINDEX and UPDATE STATISTICS on all tables in the database to (hopefully) improve performance. The question I have is this; if I start a job running to do these, what will happen the next time a transaction log shipping occurs? Will the secondary database immediately start doing the same operations as the primary? Will it do that once the primary has finished? Or do these operations not get logged at all and therefore I'd have to do the same jobs on the secondary database manually?
Thanks in advance
Niall
August 24, 2006 at 10:49 am
your re-index and stats will create large logs which will also get shipped. If you have a window where users don't connect and the log shipping isn't microsoft then stop the shipping - put the database into simple, do your stuff, put it back to full, back it up, start log shipping again. If the database is in full recovery then all the ops will get logged.
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply