September 16, 2005 at 1:59 pm
I have a set of master data that needs to sit on a common database. This common data will be used in several other user db's. Normally, you preserve referential integrity by creating a relationship between primary and foreign key tables....when all the tables are located within the same db.
So for example, the customers master data table sits in the common database, but the customerID in that table will be used in other databases.
Does anyone have any good strategies to simulate or force key constraints between the db's to ensure incorrect customerID's don't get recorded in the user db's?
September 16, 2005 at 4:07 pm
Triggers that read values from other tables in the other database.
Thats a tough way to build a system.
I've seen other posts like this, but I don't know that there has been a viable solution to handling this type of issue.
You can also do it outside of the database in the application business layer using transaction handling for a multi database commit. But from a database perspective there will be no way to guarantee ACID database.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply