Mr or Mrs. 500
Comments posted to this topic are about the item Stairway to SQL Server Replication: Level 3 - Transactional Replication – The Publisher
Good article. Didn't see it mentioned but Non-Clustered indexes are not created on the subscriber automatically. When you view the article properties, you would need to select this option. Some may not need them, but if you are using this for reporting, it is recommended that you enable this option for the snapshot. I didn't realize this when I first set up mine, and had to go back and modify my publications.
Reading through this .. so we can set up replication from the data warehouse to the various app db servers. Once question that jumps out at me is the effect of commands like BULK INSERT and TRUNCATE TABLE.. in replication process. Do they get skipped.. thus never updating the target db/tables? (Transactional Replication)
One issue that I seem to have missed in this stairway.. If you are looking at Transactional Replication... you MUST have PK set on the tables you are replicating.. this is an issue for our inventory data, since our software has this data vectorized and what is tuple 129 today holds no relation to what is 129 tomorrow. The only way I can see to handle this.. is by snapshot.
Question: How to publish a remote database from another Publishing and Distribution server? For example:
Database AAA in Server1(Read-Only) <-- Publishing and Distribution server (Publication Database AAA) <-- Subscription Server
Any comments or suggestions?
Viewing 5 posts - 1 through 4 (of 4 total)