Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Single Data Base with Multiple Schemas Expand / Collapse
Author
Message
Posted Monday, September 9, 2013 6:48 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, September 20, 2013 3:30 PM
Points: 2, Visits: 17
Hi, my name is Carlos, I'm using SQL Server 2012, and I have a situation, my boss wants to integrate every Data Base in one single, but I'm not sure 'cause maintenance will become hard. By example, One of those DBs, belongs to a real-state sales management (17 GB), another DB to a judicial processes management (5 GB), the backup time will increase, if something goes wrong with files or schemas, every Application will be afected.
Well, my questions are:

In which cases is recommended doing this centralization?
What are the best practicess recommended?


thanks for comments, regards.
Post #1492963
Posted Tuesday, September 10, 2013 3:40 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 4:03 PM
Points: 14,017, Visits: 28,396
If these are completely different functional applications with no shared data between them, then no, I would not put them into the same database. The sizes you're talking about are fairly small, so taking a 10gb database and making it 15gb is pretty trivial, so I wouldn't argue from that stand point. Instead, I'd worry about the fact that deployments to one application will affect the up-time and availability of the other. I'd worry about the fact that you've got users in the database that shouldn't have access to other apps, so now you have to get security set up differently within each database. As a general rule of thumb, if they're not sharing data, don't put them into the same database.

Just a thought, is your boss an Oracle person? They refer to a database what would, on the SQL Server side, be basically an instance. So they think they need to jam everything into one db when they don't.


----------------------------------------------------
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood..." Theodore Roosevelt
The Scary DBA
Author of: SQL Server Query Performance Tuning
SQL Server 2012 Query Performance Tuning
SQL Server 2008 Query Performance Tuning Distilled
and
SQL Server Execution Plans

Product Evangelist for Red Gate Software
Post #1493066
Posted Tuesday, September 10, 2013 8:08 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, September 20, 2013 3:30 PM
Points: 2, Visits: 17
Thanks, I agree with you about performance, availability, and security. I most work in planing, and yes you're right, my boss worked with Oracle, at least 8 years.
Post #1493205
Posted Tuesday, September 10, 2013 9:22 AM
Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: Friday, October 31, 2014 8:29 AM
Points: 519, Visits: 151
Grant Fritchey (9/10/2013)
..
Just a thought, is your boss an Oracle person?


That was a very clever observation, also a time-saver
Post #1493254
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse