As you can tell, designing a technology solution to meet all of your requirements optimally is by no means straightforward or easy. You will win some
In terms of your disk subsystem, you did not really sacrifice disk performance in going from the larger disks to the smaller ones. Most people prefer smaller, faster disks. The problem you now face is that you intended to use some combination of mirroring and striping but only did so on your OLTP data, exposing your system databases to a potential availability problem or tempdb performance problem. Not having the testing environment hardware is starting to come into play. Because of the sheer number of disks (97) now involved in your solution, you need to stock spare drives to be used at a moments notice. Your risk exposure on the OLTP disks is less than, say, your system databases, but if enough
Unfortunately, cost always has to be addressed in the trade-off mix of cost, performance, growth, and availability. It is not easy to achieve all of those while staying at or under budget. In fact, most people do not have a $500,000 budget for just the database portion of the hardware; the budget might be for all servers or (
Remember to do checks, both real and in your head, during the entire process. Some questions you can ask are listed below; there will be more that are project specific. Hold regular meetings to make sure everyone is in agreement that the solution is right.
Does the architecture seem sound? What are the potential flaws?
Is the solution you designed supportable or is it too complex? Is it flexible and scalable? Or is it too rigid, and will it be
Does the solution meet the availability requirement? Are there any risks or points of exposure?
Does the solution fit the budget, or does there need to be some compromise? If so, where would you make trade-offs? Consider questions like these:
Where would you place the most memory or processors?
Are you valuing performance over availability?
Do you design a base level of hardware first and build from there?
Did you consider special requirements such as the quorum disk or domain connectivity if you are using a cluster?