4 ms·
>By the time you've forked out for the (now suddenly per core rather than CPU[1]!) enterprise license, all the 3rd party backup and restore tools, numerous wind
by incision 14y ago
>By the time you've forked out for the (now suddenly per core rather than CPU[1]!) enterprise license, all the 3rd party backup and restore tools, numerous windows licenses and had your arse audited for license compliance, you're down a lot of cash.
SQL Server licensing is pure madness.
I will never forget sitting across from a cadre of regional level Microsoft folks who had just finished explaining the intricacies of SQL virtualization licensing.
The seemingly straightforward design we envisioned to cost perhaps $120K under any sort of reasonable, logical licensing structure attached to per socket price of SQL would actually run upwards of $1.3M to properly comply with the Microsoft licensing terms.
It wasn't even the absurd total or the ridiculous terms that were so memorable. It was the fact the Microsoft folks seemed to be as shocked at our incredulity as we were at their terms.
I got the impression they weren't used to providing more than "It's cheaper than Oracle" as justification to receive millions of dollars.
- duncan_bayne 14y agoAt least you got a number. A company I worked for back in New Zealand had a particularly odd architecture which didn't fit neatly into any of the SQL Server licensing structures at the time. We asked MS what sort of licences (& how many) we'd need to purchase and were still waiting for an answer months later when I left.
- noonespecial 14y agoI worked on one of those myself. The truly ass-backwards thing about it is that MS sales won't tell you what licenses you should buy in advance... but they'll sure as hell tell you what you should have bought during the audit.
- meaty 14y agoYes - we've just been royally raped by this. It's mainly down to virtualization and MSDN license coverage though. Screw them - we're moving some of our shit to Java/Linux (some of it is already there).