We help IT Professionals succeed at work.
Get Started

Replikation on SQL 2000 distribution DB is too big!!

ICSAutomation
on
626 Views
Last Modified: 2012-05-05
Hello
I have two servers with Windows Server 2003 SP1 and SQL Server 2000 SP4 where I have a Replication (Transactional publication)

Now, somehow, 20 days ago, the replication stoped and the distribution DB started to grow. Yesterday the SQL stoped and I have following Application-Event Error from the MSSQLSERVER

Event ID: 17052
Error: 9002
Severity: 17
State: 2
The log file for database ' ' is full. Back up the transaction log for the database to free up some log space.

I deleted the abonnement on Server 2 and recreated a newone. Then I started a snapshot.
The Replication is now active again.

But now my question:
- Why did this happen? There is plenty of free space on th disk.
- The distribution DB (distribution.MDF) has still 3.5 GB, but there are no open transactions. (Replikation is synchonized) How can I shrink it?
Comment
Watch Question
This problem has been solved!
Unlock 2 Answers and 2 Comments.
See Answers
Why Experts Exchange?

Experts Exchange always has the answer, or at the least points me in the correct direction! It is like having another employee that is extremely experienced.

Jim Murphy
Programmer at Smart IT Solutions

When asked, what has been your best career decision?

Deciding to stick with EE.

Mohamed Asif
Technical Department Head

Being involved with EE helped me to grow personally and professionally.

Carl Webster
CTP, Sr Infrastructure Consultant
Ask ANY Question

Connect with Certified Experts to gain insight and support on specific technology challenges including:

  • Troubleshooting
  • Research
  • Professional Opinions
Did You Know?

We've partnered with two important charities to provide clean water and computer science education to those who need it most. READ MORE