Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
john.burns
Posting Yak Master
100 Posts |
 Posted - 2007-01-23 : 13:31:04
|
| Every sunday my reindex job runs and when it goes up against the largesttable in db (90,000,000 rows) the reindex takes very long.. not sure exactly but the job which is around 20 reindex commands takes around six hours to complete.While this job is running my replication logreader times out and fails causing manualintervention.DB is 120GBTLog is 25GBShould the tlog be smaller. I've always read that Tlog should be sized around 1/4 the size of the db?Any ideas what to do about replication failure?Thanks! |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2007-01-23 : 15:52:50
|
| If you run DBREINDEX on the entire database each time, the TLog will be at least the size of the MDF file. I've seen it be 1.5 times the size too. Add retry steps to the logreader job that way no manual intervention is required. You can also change the profile of it.Tara Kizer |
 |
|
|
john.burns
Posting Yak Master
100 Posts |
Posted - 2007-01-23 : 16:16:55
|
| Thanks Tara,DB is in simple mode so presume this is why it does not grow even larger.I will boost the retry attempts and see how that works. |
|
|
|
john.burns
Posting Yak Master
100 Posts |
Posted - 2007-01-24 : 09:19:14
|
| Actually I see that it was my distibutor job that timed out.Do I just create a new default profile change polling interval and save.? Do I need to stop/start replication? |
|
|
|
Kristen
Test
22859 Posts |
|
|
|
|
|
Replication Time-out with large Tlog