Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Stairway to SQL Server Replication: STEP 3 - Transactional Replication – The Publisher


Stairway to SQL Server Replication: STEP 3 - Transactional Replication – The Publisher

Author
Message
Sebastian Meine
Sebastian Meine
Grasshopper
Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)

Group: General Forum Members
Points: 17 Visits: 36
Comments posted to this topic are about the item Stairway to SQL Server Replication: STEP 3 - Transactional Replication – The Publisher
B's-Data
B's-Data
SSC Veteran
SSC Veteran (276 reputation)SSC Veteran (276 reputation)SSC Veteran (276 reputation)SSC Veteran (276 reputation)SSC Veteran (276 reputation)SSC Veteran (276 reputation)SSC Veteran (276 reputation)SSC Veteran (276 reputation)

Group: General Forum Members
Points: 276 Visits: 506
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.
dwilliscp
dwilliscp
SSC-Addicted
SSC-Addicted (418 reputation)SSC-Addicted (418 reputation)SSC-Addicted (418 reputation)SSC-Addicted (418 reputation)SSC-Addicted (418 reputation)SSC-Addicted (418 reputation)SSC-Addicted (418 reputation)SSC-Addicted (418 reputation)

Group: General Forum Members
Points: 418 Visits: 767
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)
dwilliscp
dwilliscp
SSC-Addicted
SSC-Addicted (418 reputation)SSC-Addicted (418 reputation)SSC-Addicted (418 reputation)SSC-Addicted (418 reputation)SSC-Addicted (418 reputation)SSC-Addicted (418 reputation)SSC-Addicted (418 reputation)SSC-Addicted (418 reputation)

Group: General Forum Members
Points: 418 Visits: 767
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.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search