Hi Gurus,

I did mistake again... This time again my replication failed, and now my
log file size is 12 gB...

What I did is directly made backup log with truncate only...
As my logreader failed, it has to run so as to take the uncommitted
transaction, but now my log reader is restring and my log is full,

Dbcc sqlperf(logspace)
Shows 93% used
And
Dbcc loginfo(dbnam)
Shows all 2's

Please help....



Thank you.
Vinay Thakur
GE Healthcare- Satyam Computer Services.
101 Carnegie Center, Princeton, NJ 08540, USA
T 609 514 6011
D *600 6011

-----Original Message-----
From: David Ott [mailto:[Email address protected]
Sent: Thursday, March 27, 2008 9:26 AM
To: Thakur, Vinay (GE Healthcare, consultant)
Subject: RE: Ldf file size is more then mdf file size -Publisher DB

**A LazyDBA.com subscriber has responded to your lazydba.com post**
**LazyDBA.com mail shield has forwarded you this email, **and removed
any attachments, and kept your email address secret **from this person,
and any viruses/trojans.
**If you reply to this email, the person will see your email address as
normal **Anything below this line is the original email text


This seems to be related to replication.

The issue is that the transactions stay in the log until they are copied
by the log reader and be marked as read and ok for backup/removal.

Dave
-----Original Message-----
From: Thakur Vinay (GE Healthcare consultant) [Email address protected]
Sent: Tuesday, March 25, 2008 10:15 AM
To: LazyDBA Discussion
Subject: Ldf file size is more then mdf file size -Publisher DB


Morning All,

At production on publisher Database, on Friday evening our log reader
job failed, I checked on Sunday morning, till that time it occupies all
the disk space, and what I found is backup size becomes 4 times more
then actual. and ldf size becomes 2/3 times more( it used to be less
then mdf size), After restarting the logreader agent- job, the backup
file size becomes normal, but my ldf file size is still high.... which
is a my concern...
this
is occupying most of my disk space.

Please suggest me how to handle this, as replication is going on, and I
think its not good to truncate the log.

thinks are like this:
generally:
mdf: 4GB
ldf: 3.8GB
bak: 4GB

now
ldf file size is : 8.8GB

The output of:
DBCC sqlperf(logspace)
Database 8283.7422 1.110167 0

can I shrink the ldf? ... would it impact on my replication?

*** IT IS A PRODUCTION, PUBLISHER DATABASE

Please suggest. Its critical for me.
--
Thank you.
Regards,
Vinay Thakur







---------------------------------------------------------------------
TO REPLY TO EVERYBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY To post a
dba job: http://jobs.lazydba.com To subscribe : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html




MS Sql Server LazyDBA home page