ive updated my orig post to remove "SQL" and replace w/ "data". i work for a household-name energy company and we have an immense amount of time-series data, but as ive posted on another reply this data lives in our servers (not somebody's MP). these servers are virtualized running atop blade servers...yes you may lose some performance in VM over standard, but the fact that you can hot-swap failed drives or throw more hardware resources at a bottlenecked server eliminates that shortcoming.
fair, but the discussion you & i are having (server farms) is slightly different than the one here (MP not supporting Win7 natively). nobody is dependent on a MP workstation running in bootcamp to maintain their org's backend data structure....
i know, we're mostly talking thoereticals now. But to me, If i choose that the best practice for me is to run on barebones for testing purposes, it irks me when i get hardware home, that the hardware vendor puts arbirtrary blocks on what I can or cannot do on that hardware.
this mentality of mine applies everywhere. I buy a phone for example, that hardware, if it supports running something should not be limited to onyl one OS for example because the person making the hardware for their own profit purposes demanded that I only run their OS.
The Mac pro is essentially a fancy SFF computer, that has amazing hardware potential. Don't tell me that my win7 testing now must be crippled in performance because Apple arbitrarily decided it doesn't want me running Windows 7.
I would never use a Mac pro for a server. I know that. I hope most people know that. But I would LOVE a Mac pro for my workstation test platform. Unfortunately Openedge doesn't support OSx. It is Windows or *nix only. A lot of my testing is trying to figure out the best configuration settings for the servers, as well as often doing CPU and IO intensive testing activities.
Removing Windows 7 bootcamp from Mac Pro has been the last nail in the coffin for me for my Mac Pro plan. I preffer OSx in many aspects to windows for my personal use. But, I recognise that my professional use still requires Windows 7. this limitation has put the Pro completely out of the question.
Many corporations we deal with have gone the Virtualization route. Many do it well and dont have a lot of issues with the overhead, And some have. I just finished an upgrade project for a very large overseas institution who decided that for 2014, they would ditch the server infrastructure they had before and move to an entirely virtualized setup. even with 5 year newer hardware, after claiming to us "we know what we're doing, we have several million dollars worth of equipment and expertise working on it"... we found there was a 20-30% performance degradation over their previous setup.
then I just finished another implementation that was so small that a single core Xeon was more than sufficient for their transactional needs.
I guess the whole point i'm trying to say is that there's no "right" answer. but hardware vendor imposing limitations on the software side of things is never better for the consumer because it limits their options and capabilities. in this case, in what is supposed to be a workstation computer, cutting windows 7 out, which is still the primary Enterprise platform, is bad and really doesn't help Apple move more Mac Pro's out the door. Somewhere, some accountant probably decided that keeping staff working on supporting Win7 wasn't profitable anymore compared to the volume of sales and they just decided to nix it instead. there's nothing WRONG with that. just expect the sales to adjust accordingly.
p.s. iThis chain of conversation is actually quite good and I've enjoyed it. A welcome break from the Typical Mac Rumours "Reality distortion field" that occurs.