Bladewatch.com

http://www.sswug.org/columnists/editorial.asp?id=1069

“During the course of the development some successes gave management a great deal of confidence.”

An article discussing some benefits of SQL server consolidation. Many of the banks have found they’ve reached a stage where there are 50 or 60 SQL servers for the different applications within the different business lines, as another application comes online with a SQL database requirement, another box is deployed. 

The only challenges with consolidation are political, and support based, at the moment if I take out a SQL box through patching/error/system failure, I affect one person, taking down your consolidated box will affect many teams (potentially, IT is always risk averse in that respect), also the chargeback can get complicated. 

On the basis that each team uses a percentage of the SQL server, how do I charge that back? Who pays the depreciation? Who approves additional load? With a shared infrastructure the process for this can slow down leading to individual servers being purchased anyway…

Consolidation needs to be put in place with the right processes to ensure that if I do come along and say I need a database created, that 1hr action doesn’t become a weeks’ approval, cost benefit analysis, performance benchmarking type activity, I’ll simply buy another box, making a business case about cost/time to live…

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.