August 26, 2009 at 3:14 am
Hi guys
We have replication setup between our Production and Reporting server, the distribution database which sits on the Production server is 59Gb in size and is growing, the log file is relatively small but the .mdf file is the big one. The recovery model of this db is set to simple. What can i do to reduce and manage the size of the distribution db?
Production server specs: SQL 2005 Standard Edition SP3, running on Windows Server 2003, 4x Intel Pentium processors, 4Gb Ram.
Thank you
Ru
August 26, 2009 at 5:24 am
Check first of all that Replication is working fine. What is the latency of replication of the data?
Also check if db has grown to 59 GB what is the free space avialable?
HTH
---------------------------------------------------
"Thare are only 10 types of people in the world:
Those who understand binary, and those who don't."
August 26, 2009 at 7:02 am
The server has some free space left but not alot, also replication seems to be working fine, no errors
August 26, 2009 at 7:17 am
What the previous poster meant was check the amount of free space in the distribution database - not the server. Just because the database is 59GB in size doesn't mean that it using all of that space up - some or most of it could be just free space.
August 26, 2009 at 8:04 am
check you table sizes. it could be that the history tables are not being cleared down by the clean up jobs
August 27, 2009 at 5:14 am
Hey guys
I realized that there was a job to clean up the distribution database, the job however has been failing for the last couple of months.
Thanks!
August 28, 2009 at 8:52 am
ruancra (8/27/2009)
Hey guysI realized that there was a job to clean up the distribution database, the job however has been failing for the last couple of months.
Thanks!
Find out why the Distribution clean up job is failing, and that will be the solution to its growth problem.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply