There will be unique indexes at the subscriber, which is almost the same thing and you can still have FKs hanging off them. If you really want the PK
attribute, you could design a post-snapshot script.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Re: Configuring subscription database as publication. ... This'll ensure that PKs don't become just unique indexes on the ...subscriber, and the PKs will be created there. ...Paul Ibison SQL Server MVP,... (microsoft.public.sqlserver.replication)
Re: merge Replication with a Notebook not in domain ... not associated with a trusted SQL Server connection.... I have set up all SQL Server login in both publisher and subscriber.Also ... Looking for a SQL Server replication book?...subscriber... (microsoft.public.sqlserver.replication)
Re: Transformable v. regular subscriptions ... manually and have some fake values selected for the excess columns....snapshot agent can't be "told" to skip the excess columns at the subsriber so ... Looking for a SQL Server replication book?... moves from the Publisher to the Subscriber.... (microsoft.public.sqlserver.replication)
Re: Newbie to Replication Subscriptions ... I'm not talking about the SQL Server agent on the publisher rather the ... For push subscriptions the publisher connects with the snapshot share on the ... publisher reads the files and bcp's them to the subscriber. ... (microsoft.public.sqlserver.replication)
Problems planning replication with a subscriber on the road ...synchronize on the road despite changes on his IP address. ... I preview problems with the changing IP address of the subscriber.... When the laptop goes on-line from a remote site it will receive a random IP ... I insist because the problem of synchronization with SQL Server... (microsoft.public.sqlserver.replication)
