Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
OracleSqlMan
Starting Member
1 Post |
 Posted - 2006-07-09 : 11:55:48
|
| I have an application that breaks down into two sets of data, Set A and Set B, for our purposes. Both Sets currently reside in the same database. Set A is a fairly static set of data, changing maybe once a week, if not less often. Set B is empty at first but it has a lot of dependencies to Set A. Items are chosen from Set A to fill Set B but never the otherway around.Here is the problem. We continue to copy the "master" database whenever a new customer signs up. The problem is anytime we have to update data on Set A we have to do it across multiple databases. Set B is never copied as its customer owned.What I would like to do is create a separate database that contains Set A data only. Whenever we have a new customer, I create a new database that contains Set B only. I have done so, but the relationships and constraints cannot be done unless I use triggers and procedures.Is there anyway to achieve what I am trying to do without using triggers and procedures?Thanks in advance. |
|
|
blindman
Master Smack Fu Yak Hacker
2365 Posts |
Posted - 2006-07-10 : 10:19:23
|
| Have you investigate Replication? It sounds like it would be appropriate for your situation. |
 |
|
|
|
|
|
Relationships and Constraints across databases