SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Reindexing Tables used in Log Shipping


Reindexing Tables used in Log Shipping

Author
Message
Paresh Randeria
Paresh Randeria
SSC-Enthusiastic
SSC-Enthusiastic (158 reputation)SSC-Enthusiastic (158 reputation)SSC-Enthusiastic (158 reputation)SSC-Enthusiastic (158 reputation)SSC-Enthusiastic (158 reputation)SSC-Enthusiastic (158 reputation)SSC-Enthusiastic (158 reputation)SSC-Enthusiastic (158 reputation)

Group: General Forum Members
Points: 158 Visits: 322
Log Ship will be insync once you follow steps.

I suggest, pl verify on test server for surity. We always do.
Divine Flame
Divine Flame
SSCarpal Tunnel
SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)

Group: General Forum Members
Points: 4211 Visits: 2816
I am not sure why people are so much ineterested in breaking log chain by changing the reocovery model to SIMPLE, just to avoid the log file growth during Re-indexing.

Use Bulk Logged Recovery Model instead to avoid the log file growth.
Benefits:
1. Full & Bulk Logged recovery models are interchangable. Interchanging Full & Bulk Logged recovery model doesn't break the log chain.
2. Once the reindexing is done you don't need to take the full/diff backups & restoring them on secondary.
3. You just need to switch back to Full recovery model again after the reindexing is done. Log backups will continue successfully after that & you should leave it all to SQL Server log shipping jobs.


Sujeet Singh
GilaMonster
GilaMonster
SSC Guru
SSC Guru (211K reputation)SSC Guru (211K reputation)SSC Guru (211K reputation)SSC Guru (211K reputation)SSC Guru (211K reputation)SSC Guru (211K reputation)SSC Guru (211K reputation)SSC Guru (211K reputation)

Group: General Forum Members
Points: 211543 Visits: 46258
Please note: 5 year old thread.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


Divine Flame
Divine Flame
SSCarpal Tunnel
SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)

Group: General Forum Members
Points: 4211 Visits: 2816
Actuly 2 new posts got added in the same thread today prior to my response, so replying to them :-)


Sujeet Singh
jblovesthegym
jblovesthegym
SSC-Enthusiastic
SSC-Enthusiastic (148 reputation)SSC-Enthusiastic (148 reputation)SSC-Enthusiastic (148 reputation)SSC-Enthusiastic (148 reputation)SSC-Enthusiastic (148 reputation)SSC-Enthusiastic (148 reputation)SSC-Enthusiastic (148 reputation)SSC-Enthusiastic (148 reputation)

Group: General Forum Members
Points: 148 Visits: 214
GilaMonster (2/20/2012)
Please note: 5 year old thread.


SOME POSTS in this thread are indeed over two years old, but the one immediately preceding yours answers a lot of questions I was going to pose (as I am looking after log shipping of over 50 dbs on SS2K) on the forum.

Kudos to the man. Smile
hipyskipy
hipyskipy
Forum Newbie
Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)

Group: General Forum Members
Points: 1 Visits: 140
I also have a very large database with very sizeable clustered indexed tables. I've been looking for a way around the bloating of logs and keeping tranlog backups at a decent size. The only way I have found to do this efficiently is to spread the workload throughout the week instead of doing one-shot reindexing/reorg of the database on the weekend.

Also, one comment about Devine's post. Step #2 is fine, but remember that switching to bulk-logged recovery most often increases the size of the transaction log backups (although it does keep transaction log size smaller). This is because the pages that are modified during reindexing are marked in the transaction log, then when the tranlog backups occur .. then all of the pages marked are copied into the tranlog backup. Even when using 2008+ compression, redgate, or litespeed .. these log backups can very easily clog a WAN connection.
GilaMonster
GilaMonster
SSC Guru
SSC Guru (211K reputation)SSC Guru (211K reputation)SSC Guru (211K reputation)SSC Guru (211K reputation)SSC Guru (211K reputation)SSC Guru (211K reputation)SSC Guru (211K reputation)SSC Guru (211K reputation)

Group: General Forum Members
Points: 211543 Visits: 46258
jblovesthegym (4/18/2012)
SOME POSTS in this thread are indeed over two years old, but the one immediately preceding yours answers a lot of questions I was going to pose (as I am looking after log shipping of over 50 dbs on SS2K) on the forum.


Worth noting that the info given in the post you mention is lacking a few very critical points.

Maybe take a read through this before you go off and use bulk logged recovery. It does have some downsides, it's not always interchangeable with full recovery (eg when there's mirroring), there are some risks to running it and it won't reduce the size of your log backups.

http://www.sqlservercentral.com/articles/Recovery+Model/89664/

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


Divine Flame
Divine Flame
SSCarpal Tunnel
SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)

Group: General Forum Members
Points: 4211 Visits: 2816
GilaMonster (2/15/2013)
jblovesthegym (4/18/2012)
SOME POSTS in this thread are indeed over two years old, but the one immediately preceding yours answers a lot of questions I was going to pose (as I am looking after log shipping of over 50 dbs on SS2K) on the forum.


Worth noting that the info given in the post you mention is lacking a few very critical points.

Maybe take a read through this before you go off and use bulk logged recovery. It does have some downsides, it's not always interchangeable with full recovery (eg when there's mirroring), there are some risks to running it and it won't reduce the size of your log backups.

http://www.sqlservercentral.com/articles/Recovery+Model/89664/


You are right Gail. Indeed, I should have added in my post that using the bulk logged recovery model will not reduce the size of log backups. It will only protect the transaction log files from growing very large without breaking the log chain.


Sujeet Singh
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search