SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SQL Server 2012 Insane Licensing Price!


SQL Server 2012 Insane Licensing Price!

Author
Message
Jeff Moden
Jeff Moden
SSC Guru
SSC Guru (89K reputation)SSC Guru (89K reputation)SSC Guru (89K reputation)SSC Guru (89K reputation)SSC Guru (89K reputation)SSC Guru (89K reputation)SSC Guru (89K reputation)SSC Guru (89K reputation)

Group: General Forum Members
Points: 89491 Visits: 41144
hmischel (5/16/2014)
I am not very interested in the price difference between SQL Server and Oracle.

I need to deliver database performance and reliability to our Fund and stay within budget

Our annual SQL Licensing just went from under 200K to just over 600K.

Clearly this is not going to work for use and MSFT has just lost a customer that has had SQL Server for over 18 years.

Herb



I believe that you're not considering a huge set of costs. You'll have a huge amount of lost learning all the way from the Help Desk, through the Developers, up through the DBAs, and even with Managers and PMs. You'll also have to consider any impact you might have on your applications, backup systems, replication systems, DR systems, etc, etc, ad infinitum. True "Portability" between unlike RDBMSs simply does not exist even if your ORMs can handle it.

And, to be blunt, you shouldn't need 40 core to support "about 200 users" even on the worst day and changing RDBMSs isn't going to change that. Actually it might... depending on what you change you, you may, indeed, need 40 core depending on the condition of your code. ;-)

Whatever you decide, be very, very careful to fully identify ALL the hidden costs because they can be huge, indeed. Even something as simple as not having as many forums to go to can have a major impact in development costs (never mind the lost learning that I previously identified).

--Jeff Moden

RBAR is pronounced ree-bar and is a Modenism for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
If you think its expensive to hire a professional to do the job, wait until you hire an amateur. -- Red Adair

Helpful Links:
How to post code problems
How to post performance problems
Forum FAQs
paul.knibbs
paul.knibbs
SSCrazy
SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)

Group: General Forum Members
Points: 2617 Visits: 6232
About that: have you checked what the per-user licensing price would be for 200 users? When you have so many processor cores with so few users, it might actually work out cheaper than getting the per-core licensing you're looking at.
hmischel
hmischel
Grasshopper
Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)

Group: General Forum Members
Points: 16 Visits: 20
I am not sure where you picked up a 200 user number, but that really isn't relevant.

When considering the type of activity we do, 20 cores is not a lot.

When running high speed quant trading or risk simulations or market data scrubbing, you need a serious amount of horsepower.
Simple OLTP is not the issue.

In speaking to MSFT, the strategy they are offering is downsize to standard edition where possible and consolidate on Enterprise where feasible.

That works to a point.

Obviously we cannot move our entire enterprise operation overnight.
However, we were a firm that has moved most of our systems off of Sybase to SQL Server over the past several years. We were content to stay with SQL as a single "go to" Database.

The new pricing model has compelled us to bring in other RDBMS vendors and starting with the simpler applications, we will be moving away from SQL Server.

Based on last quarters earnings, it looks like the Tier 1 customers (Big banks) had no issue with the price increase as SQL Server revenue exceeded expectations.

Lets see what happens with the secondary markets. I believe many small to midsize firms who are enterprise users will not quickly upgrade with this new pricing model.

I believe MSFT may be starting to feel this pressure as I am for the first time hearing about discounts on SQL 2014.

I think the loss of a large number of midsize firms would create a vacuum that other RDBMS would rush to fill.

It is not difficult to create a Transact-sql clone if the market exists.

Herb
paul.knibbs
paul.knibbs
SSCrazy
SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)

Group: General Forum Members
Points: 2617 Visits: 6232
I suspect both Jeff and I got the 200 user figure from the original post in this 18-month old thread you resurrected... Rolleyes
hmischel
hmischel
Grasshopper
Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)

Group: General Forum Members
Points: 16 Visits: 20
Sounds about right - I'm usually about 18 months behind on most things ;-)
Markus
Markus
Hall of Fame
Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)

Group: General Forum Members
Points: 3095 Visits: 3778
The price certainly went up when they changed the pricing model for SQL2012. It certainly opens the door to other, less known RDBMS like MySQL and EnterpriseDB.

I know we are holding off upgrading as I cannot justify the massive $$ until we have to. The number of servers here would be a huge cost with very little bang for the buck at all.



Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search