Best Practices for Multi-Department Databases

Discussion created by Jason_Farnsworth on Apr 27, 2015
Latest reply on Apr 27, 2015 by Mike_Mitchell

Hello all,


I have a project coming up that is now an addition to another project that was completed (if one can ever say completed).


The first project was for one department of a City Government, done working great. The second is for another like department that could use parts of the original departments info (ie customers). When creating the first project the second was not consider in any way as part of the scope of the overall project.


How should I create the second database? I have gone over back and forth in my mind best ways to tackle it. Should I just add to the original db and grow its ability? Should I pull out like tables and create a common db that each looks to for like data? Should I build a second for the new of use external connections for the like tables?


Any thoughts are appreciated