Best replication if the table don't have primary key

See more:

SQL

Microsoft

SQL-Server-2008R2

Hi there,

Please help me.

If we don't have pk and uk in a table for the replication and we need to reduce the latency while loading a report at a particular period of time n my application. Please suggest the best way to do it? Which replication is better? or do we have any alternative other than replication?

Please help

THank you

What I have tried:

1. We know that, at a particular period of time, we cannot able to view the report. This is the major issue. We are using Snapshot replication since the tables involved for the replication which doesn’t have a primary key.
2. Went through the types of Replication such as
a. Snapshot replication:
b. Merge replication
c. Transactional replication
d. Bi directional transaction replication
e. Peer to peer replication
3. If we work with any one of these replications, we can alter a column such as adding or dropping a column or multiple columns, etc.
4. We know that the tables which are involved for this replication does not have any keys (neither primary key nor a unique key). Analysed every replication type to pick the best replication which helps in our case.
5. As per the analysis, Snapshot and Merge replication can support even the tables don’t have primary key whereas for the Transaction, Bi direction transactional and Peer to peer replications the tables must have primary key or unique key to work with them.
6. To overcome the issue specified at the top, the snapshot replication is the bad option where is the data will be static most of the time.
7. Since our data is changing very often, we can go for Transaction replication or bi directional replication. The issue is the tables which are associated must have primary key on them.
8. Gone through the old back up technique concepts called ‘Data Mirroring’ and ‘Log Shipping’ which is not straight forward concepts as replication does.