Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Stairway to SQL Server Replication: STEP 3 - Transactional Replication – The Publisher Expand / Collapse
Author
Message
Posted Monday, February 14, 2011 10:37 AM


Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Tuesday, August 9, 2011 7:01 AM
Points: 15, Visits: 36
Comments posted to this topic are about the item Stairway to SQL Server Replication: STEP 3 - Transactional Replication – The Publisher
Post #1063696
Posted Wednesday, November 20, 2013 8:52 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Friday, May 27, 2016 8:02 AM
Points: 269, Visits: 485
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.
Post #1516092
Posted Tuesday, May 24, 2016 12:32 PM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Friday, May 27, 2016 6:54 AM
Points: 397, Visits: 730
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)
Post #1789408
Posted Tuesday, May 24, 2016 12:36 PM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Friday, May 27, 2016 6:54 AM
Points: 397, Visits: 730
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.
Post #1789410
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse