[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 588
  • Last Modified:

Replikation on SQL 2000 distribution DB is too big!!

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?
0
ICSAutomation
Asked:
ICSAutomation
2 Solutions
 
David ToddSenior DBACommented:
Hi,

I've seen the logfile is full a couple of times. My guess is that one thread has requested space, and the file is growing to furfill that request, when another reqeust for space gets dennied. Growing the files does take a finite amount of time.

Cheers
  David
0
 
ICSAutomationAuthor Commented:
I didn't change anything but the file is not growing anymore.....
No clou why it happend....
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now