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 |
|
jp2code
Posting Yak Master
175 Posts |
 Posted - 2009-06-14 : 22:36:07
|
I'm not the most enlightened database architect, and I've just been asked to come up with a design as described below:A central database will be in the cloud and house everything.Let's say I have 2 users: Rod and Sam. These are my remote users who will be running applications to build their databases on their personal workstations independent of the "cloud" database.When Rod syncs his application with the "cloud" database, all of Rod's information will be written and the "cloud" database will retain that the data was contributed by Rod.Rod can modify this data and update it as needed.Sam can download and use Rod's data, but the only way they can modify it is if Sam creates his own project for the data to run under. Then, it becomes Sam's data. When it gets saved, it is saved under Sam's section.How would I design something to keep track of who's data is who's?
Avoid Sears Home Improvement |
|
|
|
|
|
DB design