May 21, 2012 at 4:10 pm
Hi all,
my department works on several different projects, all of them on SQL Server 2008 and on the same server.
Each project has it's own database, user interface, etc.
However, they all share common data: Country, Products, Clients. These tables have been put on another database, called REFERENCE, still on the same server.
The problem is about foreign keys, in the projects, that cannot reference the REFERENCE data (FK can't work on different dB).
My question is about best practices here, knowing that Projects database should not modify the REFERENCE data:
- Should I copy the REFERENCE db into a particular schema of each project and synchronize any modification from the REFERENCE dB to the Projects (what is the best way to synchronise ? Triggers ?)
- Should I stop using foreign key in projects (:ermm:)
- Any other suggestions ?
Thanks !
Bruno
May 21, 2012 at 5:12 pm
Replication.
Replicate out from the Reference db to the other dbs, moving those common objects.
May 21, 2012 at 6:20 pm
Thanks Steve,
after googling, seems like this is exactly what I need !
Cheers,
Bruno
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply