merge replication without rowguid

hi,
I have a database that has Primary Key constraints on every table. Yet
when I run the replication wizard and try to configure merge
replication the wizard notifies me that it will create a rowguid on
the tables even though they already have a primary key.
anybody know how to avoid the rowguid column from being created?
regards,
Doron
what is the big deal with having rowguid column?
I am running the replication for 3 years with that column without any
prolem!
"DoronA" <doronal@.msn.com> wrote in message
news:OMPe$RgwEHA.824@.TK2MSFTNGP11.phx.gbl...
> hi,
> I have a database that has Primary Key constraints on every table. Yet
> when I run the replication wizard and try to configure merge
> replication the wizard notifies me that it will create a rowguid on
> the tables even though they already have a primary key.
> anybody know how to avoid the rowguid column from being created?
> regards,
> Doron
>
|||If your primary key is a unqueidentifier, then you can mark it as the
RowGuid column using ALTER TABLE, e.g.
ALTER TABLE dbo.MyTable
ALTER COLUMN MyPK ADD ROWGUIDCOL
Otherwise, you have to have a separate RowGuid column, as it's how
replication tracks the global identity of rows.
Paul
"DoronA" <doronal@.msn.com> wrote in message
news:OMPe$RgwEHA.824@.TK2MSFTNGP11t .phx.gbl...
> hi,
> I have a database that has Primary Key constraints on every table. Yet
> when I run the replication wizard and try to configure merge
> replication the wizard notifies me that it will create a rowguid on
> the tables even though they already have a primary key.
> anybody know how to avoid the rowguid column from being created?
> regards,
> Doron
>

merge replication without rowguid

hi,
I have a database that has Primary Key constraints on every table. Yet
when I run the replication wizard and try to configure merge
replication the wizard notifies me that it will create a rowguid on
the tables even though they already have a primary key.
anybody know how to avoid the rowguid column from being created?

regards,
Dorondoron_almog@.msn.com (Doron) wrote in message news:<995517bc.0411031605.30cf6318@.posting.google.com>...
> hi,
> I have a database that has Primary Key constraints on every table. Yet
> when I run the replication wizard and try to configure merge
> replication the wizard notifies me that it will create a rowguid on
> the tables even though they already have a primary key.
> anybody know how to avoid the rowguid column from being created?
> regards,
> Doron

Unless all of the replicas are read-only, how would you prevent the
same PK being allocated to two different rows in two different
replicas?

The solution you are being offered is to have rowguid be the primary
key - what's your proposed solution to the problem?