November 24, 2008 at 4:47 am
I have an database developed in SQl Server 7 which uses 'Identity' fields on all tables to identify each record within. A web application then uses these identities to fetch, sort, etc, data and then display it on screen. We are now looking at replicating the SQL database (now ported to SQL 2005) at another location in the country. Having read a few articles I am thinking 'Transaction Replication with immediate update' i.e. both sql instances can read/write and publish their changes to the relevant subscriber, however, what happens with indentities. It is possible to create a record on each machine with the same identity but a seperate record. My database is vast aswell as my web application, and I dont want to have to recode all those pages to cope with replication data.:w00t:
November 24, 2008 at 5:17 am
I think I am starting to get my head around this now. Am I correct in thinking that Database A uses Identities (pre arranged) 1 to 10,000 for example and database B uses 10,001 to 20,000. When database A adds a new record eg 3456 it publishes that to Database B using the same ID (3456) when Database B adds a new record (13,456) it publishes that to Database A as 13,456.
OK I understand that bit, but how do I now setup all my tables as you cant insert an ID (it is auto generated and incremented by the box). Is that a 'behind the scenes' action for SQL Server wizardry routines that I "need not worry my pretty little head over there's a good boy" 😀
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply