Click here to monitor SSC
SQLServerCentral is supported by Redgate
Log in  ::  Register  ::  Not logged in
Home       Members    Calendar    Who's On

Add to briefcase ««12

one db versus multipl dbs Expand / Collapse
Posted Wednesday, April 30, 2014 1:46 PM



Group: General Forum Members
Last Login: Today @ 2:52 PM
Points: 7,977, Visits: 16,005
dexdev (4/30/2014)
Seems like the correct solution would be to go with one larger db.

Clarify what you mean by one db, do you mean 1 instance?
The 2 terms have very different meanings


"Ya can't make an omelette without breaking just a few eggs"
Post #1566592
Posted Friday, May 2, 2014 10:02 PM

SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, November 18, 2015 9:28 AM
Points: 48, Visits: 468
You have a great idea here. Clustering gives you HA for the instance (memory structure, internal storage engine and background processes) but maintains a single point of data. As far as having many databases, that will pose a management struggle for the DBAs so consider consolidating them based on the various applications and / or app functions (if they are all in use by one app).
That way, you will have fewer but larger databases and you'll have to revisit your storage and maintenance strategy for them.
How many tables exist per database and what are the sizes of these databases? You might be able to consolidate but if not, I'll suggest using multiple instances to manage them (which means changes to the application connection string(s).
Please feel free to reach out for help more via email (
Post #1567208
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse