Hi there,
We have 20 tables (no primary key) to replicate from one server to other. We created two snapshot replications hourly and daily, in which 10tables are associated with hourly replication tables and the remaining 10 tables are with daily replication tables. We are planning to change the type of replication from Snapshot to transactional replication for these 20 tables in order to minimize the latency. Previously we don’t have primary key to these 20 tables, in order to work with transactional replication we need to have a pk so I created a new database and added the tables with primary key and identity property to all, and dumped these tables in the new database.
We are working with a live stage server where the snapshot replication already exists (running) with those 20 tables. I used this newly created database tables to replicate from this stage server to other for testing, so I created two transactional replications hourly and daily on the stage server with those 20 tables (with pk). And I maintained the scheduled jobs between the tables for snapshot and transactional replication with minimum gap of 4 hours (for daily replication tables) and ½ an hour (for hourly replication tables).
The transactional replication is successful, as our target to reduce the latency as compared to snapshot replication. But the problem is, the other jobs in this live stage server are running slow (sometime after creation) as compared to earlier. I am not sure, after I created the transactional replication, is this problem got raised or do we have any dependency while using the same tables with different schema?
Please help me. The version I am using is sql server 2012.