Distribution database is 9 GBs

Our distribution database in up to 9 GBs, after only 3 weeks...
What job cleans out data from this database?
What do I need to check to verify this?
Thanks and God Bless,
ThomBeaux
Is that all. What's your secret?
Check space usage to see if this is the actual size and ensure its not the
transaction log bloat.
The distribution database is a queue which is purged by the distribution
clean up task. For anoymous subscribers you can get data hanging around till
the retention period has elapsed (or the lesser of the retention period and
the history).
It is normal for it to grow quite large if your publisher is replicating a
lot of commands.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"ThomBeaux" <ThomBeaux@.NoSpam.Com> wrote in message
news:9421D30A-1F0D-4CC8-8980-00C09DDA6837@.microsoft.com...
> Our distribution database in up to 9 GBs, after only 3 weeks...
> What job cleans out data from this database?
> What do I need to check to verify this?
> --
> Thanks and God Bless,
> ThomBeaux
|||Primary Data is: 12.68 GB , 12.67 Used
Transaction Log: 9.9 GBs, 81.8% used.
Log and data files are growing by the hour.
What Agent Job should I watch to see if it is being cleaned out?
This system was just updeated to 2005, and we never had a distribution
database larger than 4-5 GBs in 2000, with the same system.
Thanks for the responce Hillary. I see your signature on lots of rpelication
issues, and it is appreciated. Will you be at PASS in denver?
Thanks and God Bless,
ThomBeaux
"Hilary Cotter" wrote:

> Is that all. What's your secret?
> Check space usage to see if this is the actual size and ensure its not the
> transaction log bloat.
> The distribution database is a queue which is purged by the distribution
> clean up task. For anoymous subscribers you can get data hanging around till
> the retention period has elapsed (or the lesser of the retention period and
> the history).
> It is normal for it to grow quite large if your publisher is replicating a
> lot of commands.
> --
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "ThomBeaux" <ThomBeaux@.NoSpam.Com> wrote in message
> news:9421D30A-1F0D-4CC8-8980-00C09DDA6837@.microsoft.com...
>
>