> Interesting. We do a lot of replication (snapshot/transactional) and have > not had a problem with identity columns. Only with foreign keys to other > databases (obvious when you realise there is no way a replication of one > database can gaurantee a foreign key in another database also exists on > the replica destination).
Yep that's right. It was foreign keys that were the main issue. I guess we could have setup triggers to set the foreign keys but it was just as easy to code around the problem. > So - to sum up - you had no problems with allowing SQL*Server to add it's > rowguid column and replication seems to work fine (given other general > constraints with SQL replication not related to FarCry)=3F Well I wouldn't say it was a walk in the park because they wouldn't let me access the database and the 'DBA' had never done replication before! But once he'd worked it out it all worked fine. --- You are currently subscribed to farcry-dev as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004
