opc.three (7/27/2011)

---

David Benoit (7/12/2011)

---

Great. I will follow-up later with a bit on subscriptions and the impact of removing them.

Let me know if you have any problems with the article...

Yes, read the blog and appreciated the information. We have run into most of those issues as well. I did find some suggestions to eliminate the need for reconfiguration with...

Great. I will follow-up later with a bit on subscriptions and the impact of removing them.

Let me know if you have any problems with the article drop. You shouldn't....

Yes, force_invalidate_snapshot = 1 is identical to the warning in the GUI. Only run the sp_droparticle statement though not the sp_dropsubscription statement that you have. You really don't want to...

You can drop the article with the subscriptions in place and yes it will invalidate the snapshot. However, if you were going to use the snapshot again later for a...

scott.shaw (7/12/2011)

---

I've written a few articles at MSSQLTips concerning implementing SMSQL and also testing backup times with snaps and streaming backups. http://www.mssqltips.com/author.asp?authorid=55.

We implemented SMSQL on a grand scale starting...

Excellent - glad that worked and thanks for the update.

As Gail stated you should really start a new thread. When you do please post the link in this one so that I know where it is.

For now though,...

What specifically is the problem? Is your log reader agent running?

GilaMonster (7/5/2011)

---

I'm not one of the editors, but this site publishes what volunteers write and submit. You can request articles (there's a forum specifically for that), but you can't force...

The following is according to BOL;

"Changing any of the following properties requires that existing subscriptions be reinitialized, and you must specify a value of 1 for the force_reinit_subscription parameter.

del_cmd

dest_table

destination_owner

filter

ins_cmd

status

upd_cmd"

So,...

Great point Michael. You could also just run a trace on the subscriber with the application name being that of the distribution agent and you can see what you are...

Log Reader will continue to move the records from the transaction log to the distribution database. You will want to leave that running so you don't get t-log bloat. The...

I have to step away but can help later again. In the meantime, are you sure that the snapshot completed successfully? Are you seeing the error in the distribution agent?...

You could delete the duplicate record on the subscriber and that would allow replication to insert the identical record. You could also delete the transaction from the distribution database by...