Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

What Happened:

I reinitialized a subscription 16 hours ago. I had about 1.2M records to transfer, so I was expecting it to take a while. The Replication Monitor was saying "N transactions with N commands were delivered" for hours, so I figured everything was OK.

The Issue:

This morning when I check the Replication Monitor, I see this: Snapshot Not Yet Available

Oh no!, I exclaim, thinking I need to reinitialize replication with a newer snapshot to avoid pulling 1.2M rows. But I look at the other Tab on the Replication Monitor, and I see this:

Transaction Delivered


I'm wondering why Transactions are being delivered, despite Replication Monitor complaining about the snapshot.

share|improve this question
up vote 1 down vote accepted

It's hard to say exactly but it looks like something went wrong during the reinitialization process. Transactions are flowing from Publisher to Distributor but the Subscriber is requiring a new snapshot. I'd recommend generating a new snapshot and then it will be reapplied by the Distribution Agent. At that point you should be back in sync.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.