|
|
Posted by SQLNow on 07/11/05 14:05
Adding a primary key would be the best, but it is not an option.
The table volumes are huge and I was hoping that SQL Server replication
would manage all the uniqueness of the tables to be replicated. I was
reading that there may be away to do this type of replication.
"Simon Hayes" <sql@hayes.ch> wrote in message
news:1121065474.050425.75340@g47g2000cwa.googlegroups.com...
>I don't know about the replication part of your question, but why not
> simply add a composite primary key on the three columns? If that's what
> your data model looks like, then the key should be there, or at least a
> UNIQUE constraint, if you need to use an artificial key for some
> reason.
>
> For replication issues, you might get a better response in
> microsoft.public.sqlserver.replication
>
> Simon
>
Navigation:
[Reply to this message]
|