Thanks Gail.

I see, thanks for taking the time to explain Gail.

This almost seems like a problem with SQL Server then in what I've experienced :crazy:

Yes I'm using snapshot replication, and manually ran the jobs required to test it was sending data across correctly. I scheduled these jobs to run once a day over-night.

Here's the...

Sorry for the confusion guys, certainly not meant to cause it 🙂

Is there any screen-prints I can take to help clear it up?

ps (6/20/2009)

---

That's right. If you get NOTHING in that column, nothing is preventing log file from getting truncated. Everything is running fine including your replication.

Also check if your distribution db...

ps (6/20/2009)

---

JamesNZ (6/20/2009)

---

The replication seems to be working just fine. I've just tested it and don't see a problem. Is there something I'm missing? Do I really have to re-set...

The replication seems to be working just fine. I've just tested it and don't see a problem. Is there something I'm missing? Do I really have to re-set it up...

That worked! Yay, thanks heaps guys 😎

Is there anything I need to re-do after running that command?

Thanks Pradeep , doing this now. Will post back the result.

ps (6/20/2009)

---

JamesNZ (6/20/2009)

---

Thanks for the response guys.

This is what I see with select * from syspublications . Please see attached text file.

No one I know of has been messing...

Thanks for the response guys.

This is what I see with select * from syspublications . Please see attached text file.

No one I know of has been messing with the...

This was what I ran (did a copy of the SQL through Management Studio):

BACKUP LOG [DatabaseName] TO DISK = N'D:\tranbackup.bak' WITH NOFORMAT, INIT, NAME = N'DatabaseName-Transaction Log ...

ps (6/20/2009)

---

JamesNZ (6/20/2009)

---

Thanks Paul, no I'm using Snapshot replication so I don't have a Log Reader Agent.

What else could I check to try and find out how to clear/process this...

Paul White (6/20/2009)

---

JamesNZ (6/20/2009)

---

GilaMonster (6/20/2009)

---

Check that the log reader's running. Either the log reader's failed or it's slow in getting the transactions out of the log. Either way, the log...

GilaMonster (6/20/2009)

---

Check that the log reader's running. Either the log reader's failed or it's slow in getting the transactions out of the log. Either way, the log cannot be truncated...