Tag Info

http://social.msdn.microsoft.com/Forums/en-US/sqlreplication/thread/0b8bac44-da87-4115-90f6-b8bf1e1d0bd8 Both cmd values relate to the number of commands written. Since last stats - cmds are all cmds written since the last entry and stats- cmd are an accumulation of all cmds written since the last comment with a state of 1.

Just to add that you don't have to drop and re-create the replication just to change the "not for replication" bit. You can do it using T-SQL without generating a snapshot or breaking your replication -- sys.sp_identitycolumnforreplication 1 = not for replication 0 = for replication and this causes the problems with Identity colums on subscriber side To ...

If replication is automatically creating indexes, then you probably can't avoid it. The only way to do so might be to create a matching index on the subscriber. What's the wait type of the CREATE INDEX statement?

1. Does the transaction replication have any load on the primary server(pardon my use of generic terms) when its moving data out. Many factors that it depends -- On the activity on the primary server which will be the Publisher server. Also, if the distribution agent on the same or different server matters a lot as it will be doing the heavy work of ...

1.Does the transaction replication have any load on the primary server(pardon my use of generic terms) when its moving data out. There will be an impact on the publisher, but depending on how you set up your transactional replication schema that can be very small. One big problem that can become an issue is if you have a local distributor, especially ...