C
ChUIMonster
Guest
The main risk is that they will attempt a cookie cutter "out of the box" configuration. A DB server is not a simple appliance that can be treated like some silly little thing. Watch out for: "thin provisioning", "over subscribed", "shared" and "dynamic". Those are code words for "you don't really need any resources so we aren't going to give you any". Database servers need to be provisioned for peak loads. Your peak is not the average usage over 24 hours. Nor is it what someone sees looking at 5 minutes of "busy" time in the afternoon. Peaks occur when you have to do unusual things -- month end processing, nightly data warehouse extracts, restore and roll-forward, index rebuild... and a lot of those things are done under pressure with all eyes on the system. You do not want those moments to be the ones when you discover that the system runs like molasses because the virtualization people didn't give you enough horsepower. (If it happens they will never admit it -- it will always be some variation on "Progress can't handle..." which is pure crap...) If they have never heard of Progress tell them to pretend that it is Oracle. The needs are similar enough that if they actually know what they are doing you should get a reasonable result.
Continue reading...
Continue reading...