Steve Jones - Editor (9/5/2010)

---

Glad it's working. Be sure that you have log backups running, and manage the size over time, watching the growth and balance that with the backups...

I went ahead and did the shrink anyway. I am very happy to report that the log file has now gone from 160GB to 3MB so it looks like that...

Okay Gail I've done as you said and the reference to the to the distributed and non-distributed LSNs seems to have gone away

Also log_reuse_wait_desc now = NOTHING

So I guess I...

It's definately not supposed to be set up in any kind of replication

GilaMonster (9/5/2010)

---

It means that replication (specifically transactional replication) is preventing the log space from been reused. Is this DB the publisher for a transactional replication publication?

What's the output of DBCC...

GilaMonster (9/5/2010)

---

Query sys.databases. See what the log_reuse_wait_desc is for that database.

As for the target size, that's how small you want the log. Pick a value based on what you know...

I foun this on the Microsoft site: -

DBCC SHRINKFILE (<FileName>, <TargetSize>) WITH NO_INFOMSGS

but how do I know what to set the target size to?

CirquedeSQLeil (9/4/2010)

---

Shouldn't be. Once you have a full backup and then a tran backup (and since you also manually checkpointed) you should have adequate free space in the file...

I wonder if the problem is something to do with the database running in simple recovery mode up until today?

Okay, so I went to to work on the log files to try and reduce them in size. The log files have now grown to just over 160 Gb which...

okay thanks

homebrew01 (8/31/2010)

---

I back up production log files at least once an hour. More frequently for some DBs.

Once you have a good plan in place, you shouldn't need to shrink the...

So if I had a maintenance plan that backed up the log files every so often, would that maintenance plan also need to do a shrink on the log files...

It may have been my fault as I think I might have been trying to shrink the data file rather than the log file. I tried again and this time...

So here's what I tried on a test database

The data file was 337 MB an the Log file was 1.09 GB

I backed up the log file, did a checkpoint, backed...