Criteria For Placing A New Database
-
In the environment that I'm in we have a number of dedicated SQL Servers. Virtually all are SQL2000 SP 3a & 4. Recently, there's been several requests to bring in new applications (IIS) and their associated database(s).
Is there a rule-of-thumb to determine on which SQL Server/Instance to place a new database (or when to buy a new server...). I'm hoping to draw up some kind of criteria list (or at least some questions to ask when a new application/database is presented to the SQL environment).
Does anyone have such a list -or- are there some obvious questions that should be asked?
Thanks,
Glenn
-
This is a good question I'll be curious to see some other responses. Here's a stab to get you going...
Of course, you'll have to look at your current servers...
What DBs are on which servers?
What are the current DBs functions? OLTP, OLAP?
What are the current servers hardware configs? Can you expand?
What are the current workloads on the servers?
Have you established any baseslines for your servers? If not you might want to.
How many users?
What's mission critical (I know it all is)? But try to rate them.
The new application/DB...
How mission critical is the application/DB?
Does it need to be put into a cluster?
What's the application/DB's uptime? 24x7, 8 to 5?
How many users will be accessing the application/DB?
What is the primary application use? OLTP? OLAP?
How big will the database be initially?
Can you project any growth rates based on your estimates?
Can the vendor provide any info?
Who will be supporting? Will the application vendor require access?
What's the data sensitivity? Payroll info, SSNs, Sales info, etc...?
How stable is the application? Established, new, still being developed...
How frequently does the application change, release patches/code fixes, database changes?
Hope it helps.
-
Thanks Joe - great suggestions!!!
Glenn
-
Joe has pretty much got everything covered. Although, I'd probably add one more,
How much load is the app/db processing going to put on the server?
We had an application setup recently that needed it's own hardware because it's continually running a whole pile of aggregations on the database. It's running on a dual 3Ghz Xeon and cpu usage constantly averages about 25-30%.
And another example, when I first started at my current job, the website databases and the Accounting system resided on the same server. Everytime the accounts people ran their monthly reports the website slowed to a crawl.
--------------------
Colt 45 - the original point and click interface
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply