April 25, 2005 at 10:04 am
Good Morning. Should the distribution database be set for AutoShrink? I am having replication errors, and I see that autoshrink is blocking the replication process. I inherited databases with replication, and some of them are autoshrink for distribution and some aren't. I want to make them all consistant and right.
Thanks
April 26, 2005 at 1:44 am
Autoshrink is very costly in terms of resources and can cause a lot of locking issues, not only on the distribution DB but on all others.
My personal preference is to turn it off on all DBs, and monitor their size once a week. Once you get to know your DBs and how they grow (both data and log files) , then you can shrink them either manually or schedule them in a job.
Now, please you educate me:why does a distribution DB grows and have to be shrinked?. Is the log what grows?. Or as part of a maintenance task you need to purge replication data that you no longer need?.
Thanks
Cesar
April 26, 2005 at 8:37 am
This is only my 3rd week working with replication, but I believe that it was set up to autoshrink because it grows when you do a snapshot. This is my best guess. I have very little faith in reasons why,do to the fact on how screwed up everything is on my new system. I am working one problem at a time. I will take your advice and turn off the autoshrink and watch the database. Thanks for the help.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply