merge replicaiton

Last Post 16 Jul 2006 03:47 AM by TRACEYSQL. 3 Replies.
AddThis - Bookmarking and Sharing Button Printer Friendly
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
TRACEYSQL
New Member
New Member

--
14 Jul 2006 10:58 AM
Currently we are using transactional replication but that means our TABLES have to have a primary key.
Our ERP system does not come with primary keys so we have to add them...ourselves which results in problems when we have patches as we have to stop snapshot etc...

Does merge allow you to do replicaiton without keys....

Whatst the difference...would it still carry on replicating the data.....(we replicate the data to another server so that we can report of this.

Cheers
TRACEYSQL
New Member
New Member

--
16 Jul 2006 03:47 AM
Most of our tables do have a time_stamp on it.....so i will use it if i has it ...otherwise it will add time stamp to the columns...............

By adding the timestamp to each of the tables that do not have it....(would that affect the ERP system ? )

Thanks
TRACEYSQL
New Member
New Member

--
16 Jul 2006 01:03 PM
ERP system does not support replication if they knew we were doing it be in void of our contract.
So i either have to change all their tables to have a primary key or allow the merge to take the time stamp of each table................or put time stamp into the tables and see if it works...

How any one can design a table without a primary key is beyound me ...
TRACEYSQL
New Member
New Member

--
17 Jul 2006 09:09 AM
Ok i just tested it i see it puts the rowguid on each table.

Thanks
You are not authorized to post a reply.

Acceptable Use Policy