July 8, 2005 at 2:25 pm
Do you guys think it makes sense to use one database for multiple applications if the they share data? Or would it be better to use a different database for each application?
July 8, 2005 at 3:47 pm
My personal preference is to think about a database as a related colletion of data, having nothing to do with the applications that touch it. It's been my experience that applications are transient things, but data lives forever, so putting the data togther in one unit of management (the database) makes more sense than artificially segregating it by process. So I tend to make larger databases that would support several applications. You have to worka little harder to insure data independence when you do it that way (more application specific views and stored procs) but the stability of the underlying data has seemed to result in better manageability and adapatability in the long run.
And then again, I could be wrong...
July 8, 2005 at 10:03 pm
Here's my 2 Cs...if the applications are all being developed in parallel, it's great to have one database...but if you have different db versions...development, test, production etc.. and within those you have the different db objects based on the application and you would finally "merge" these db objects at some point it can become quite a nightmare to design and maintain.....
**ASCII stupid question, get a stupid ANSI !!!**
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply