CDR and serials
Posted in 1999
Topics: High Availability & Replication, Platform-Specific Issues, Versions, Editions & End-of-Life
Can CDR handle serial values? We have an application which currently lives on the East Coast. We are considering setting up a West Coast server to handle some of the daily load. The database makes liberal use of serials, and I am not sure how the database will perform if we put it on two servers. Server Version: IDS 7.31.UC2 OS Version: Solaris 2.6 SC
Yes and No. ER uses the primary key to identify the row. If the serial column is the primary key, then it must have a unique constraint. If it is replicated and is not unique on both systems, then there will be a colision. This could cause the loss of data because the rows with duplicated serial columns would appear to be the same row. You must guarente that the primary key being used is unique. If there can be updating/inserting on both ends, then you must be able to guarentee that the PK is unique. One way to do this would be to use a composite key for the primary key, perhaps by including the server name as part of the primary key. sfcawley wrote: > Can CDR handle serial values? We have an application which currently lives on > the East Coast. We are considering setting up a West Coast server to handle > some of the daily load. The database makes liberal use of serials, and I am > not sure how the database will perform if we put it on two servers. > > Server Version: IDS 7.31.UC2 > OS Version: Solaris 2.6 > > SC