your problem is that it is possible that the same values can be
entered in both sides between syncs. to do this you will need to add a
location column to your pk.
Here is an example of how this will work - assuming TpCosto & CodSoc
are your pk columns.
CREATE TABLE [dbo].[Costo] (
[TpCosto] [varchar] (

COLLATE Latin1_General_CI_AS NOT
NULL ,
[CodSoc] [varchar] (2) COLLATE Latin1_General_CI_AS NOT NULL ,
[Location] [sysname] not null default @@servername,
[Desc] [varchar] (50) COLLATE Latin1_General_CI_AS NULL ,
[Onere] [varchar] (2) COLLATE Latin1_General_CI_AS NULL ,
[Cat] [varchar] (2) COLLATE Latin1_General_CI_AS NULL ,
[rowguid] uniqueidentifier ROWGUIDCOL NULL,
constraint CostoPK primary key (TpCosto,CodSoc,Location)
) ON [PRIMARY]
On Jan 31, 9:05 am, damar3 <dam....DeleteThis@gmail.com> wrote:
> CREATE TABLE [dbo].[Costo] (
> [TpCosto] [varchar] (
COLLATE Latin1_General_CI_AS NOT NULL ,
> [CodSoc] [varchar] (2) COLLATE Latin1_General_CI_AS NOT NULL ,
> [Desc] [varchar] (50) COLLATE Latin1_General_CI_AS NULL ,
> [Onere] [varchar] (2) COLLATE Latin1_General_CI_AS NULL ,
> [Cat] [varchar] (2) COLLATE Latin1_General_CI_AS NULL ,
> [rowguid] uniqueidentifier ROWGUIDCOL NULL
> ) ON [PRIMARY]
>
> I have the same row (TpCosto, CodSoc, Desc, Onere, Cat) in two
> database but rowguid in the two table is different. >> Stay informed about: UPDATE ROWGUID