September 2, 2006 at 3:52 pm
Greatings,
I have been working with SQL server for about 6 years now (started with version 6.5) and have been mostly doing simple administration and development. But I am setting up a new infrastructure now with bidirectional replication, to transfer a 24/7, 10g SQL Server on to. And wouldn’t you know it? it turns out to be troublesome. J
The plan was to create 3 databases on 3 servers, with all objects, proper identity column seeds (to privent "identity crisis)" and “NOT FOR REPLICATION “ options, pump data in to one of them (using replication), then set up transactional replication between the 3 databases/servers and point the web server to the new one. But every time the replication is initiated the subscribing databases(in my case all 3) looses foreign key constraints, and I have not been able to figure out why.
I am hoping that some one would have some king of inside in to this (because only someone who has done this before would) ore this would arise your interest.
In any case, any help would be greatly appreciated.
Sincerely.
Steve Rybak
September 4, 2006 at 10:19 pm
Hi,
Check whether you have unchecked the foriegn key relationship "Enforce Relationship on Replication" across all the replicated databases across these servers. Checking this could lead to the problem you have described
rangark.
September 5, 2006 at 1:27 pm
Hi,
Thanks for the reply. Where do I find this option?
September 5, 2006 at 6:30 pm
You can see part of Table -design mode.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply