Replication can be chatty and will consume significant bandwidth. With Merge Replication, even if no updates occur at the Publisher or Subscriber(s), the Merge Agent will produce traffic if...

You have options.

When using Standard Edition or higher, when a Merge subscription is created, an associated Merge Agent job is created. You start the job to synchronize the subscription.

You...

Yay! I'm glad it is working now!

EXEC sp_changepublication

@publication = 'IM_Audit_LIVE',

@property = N'replicate_ddl',

@value = 0

GO

You do realize that this statement sets replicate_ddl to false right?

If the network goes down for whatever reason, if it comes back up within the retention period, replication will pick up where it left off. It auto recovers from...

Steve Jones - SSC Editor (8/14/2014)

---

Brandon J Williams (8/13/2014)

---

My point is that replication novices are quick to point the finger at replication when it's not replication that is the problem.

We...

TomThomson (8/13/2014)

---

That seems...

dstinson-1008865 (8/13/2014)

---

Arrogant much?

The clear implication is that your own experience trumps that of anyone else because they must be a "replication novice". And that in spite of multiple other...

That's why I'm here to set the record straight.

Most of the issues I'm reading about would be helped by better reporting of replication...

quackhandle1975 (8/13/2014)

---

Brandon J Williams (8/12/2014)

---

Replication is not brittle, buggy, or unstable. Unreliable network connections can cause replication to fail, and the replication novice will interpret this as a bug...

Log shipping cannot do what replication does.

I agree, over small pipes, or an unreliable or slow network connection, replication may timeout or fail or something like that. But there...

Replication is not brittle, buggy, or unstable. Unreliable network connections can cause replication to fail, and the replication novice will interpret this as a bug or as replication being...

I know this really old guy who once said that replication is only as reliable as the network and hardware it runs on.

Locate the replication agent job in SQL Server Agent -> Jobs. Right-click the job -> Properties. Navigate to the Notifications page and uncheck Write to the Windows Application...

I agree with Gail, Transactional Replication is a better fit here considering the frequency with which you need to replicate the data. With Transactional Replication, you would only need...