AnsweredAssumed Answered

Separate DB file or not?

Question asked by amsc on Jul 1, 2018
Latest reply on Jul 1, 2018 by bigtom

In our company, our operations are divided into two different functions (call it function A and function B).  Function A handles all aspects up to a certain point, then function B finishes the work and handles logistics.  I’ve written a solution app for function B.  I’ve been asked to look at building a solution for function A.  The functions are completely different, but obviously quite related to one another.  Our corporate office wants to have a master view into both functions to see progress, bottlenecks, ... 


My question: Do I augment the current solution to include the activities for function A, or should I build a separate DB solution for function A and relate the two databases?  Broader question, when is it appropriate to split a solution into two different solutions?  I’m not talking about data separation models (i.e. gui vs data), I’m talking about separating full solutions.