December 22, 2010 at 5:11 am
We have three application in sql 2005 and we want to merge the data base
would like to know what is the advantage and disadvantage of
1) Have a separate database for all application
Or
2) Have 1 database for all application with separate schemas.
December 22, 2010 at 6:38 am
sounds like Oracle speak to me...
in SQL a database is what Oracle calls schema.
in SQL an instance is what Oracle calls a database.
so, to answer your question, each app should have there own 'database'
i only give apps their own instance IF they need to have access to the system databases. Ie master, msdb.... or if the app needs to be controlled from a resource perspective.
December 22, 2010 at 7:06 am
Before you put different applications within a single database, I'd check to see just how much cross-dependencies there are between the apps. Do they share tables & procedures? If so, you have a case for putting them into a common database. If they share nothing, or little, I'd keep them seperated because by putting them into a common database, you're going to tightly couple these apps and make it very difficult to develop them indepdent of each other.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 23, 2010 at 5:21 am
thank's for the update
the application are isolated to each othere and they use maximum simillarer tabel and SP
but fee differnet tables also .
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply