How Does SQL Server Licensing Work?
-
@Carnival-Boy said:
Oracle.
It's not just licencing costs to consider though. It's things like database administration costs.
PostgreSQL is a drop in Oracle replacement. Anywhere that Oracle works, PostgreSQL should work.
-
-
@Carnival-Boy said:
@scottalanmiller said:
PostgreSQL
Sure, but "works" and "supported" are not the same thing.
This is what I've often wondered.
-
@Carnival-Boy said:
@scottalanmiller said:
PostgreSQL
Sure, but "works" and "supported" are not the same thing.
Sucks if you have vendors that will only support expensive back ends. PostgreSQL is used by everyone today. From Wall St. To Heroku.
-
@Dashrender said:
@Carnival-Boy said:
@scottalanmiller said:
PostgreSQL
Sure, but "works" and "supported" are not the same thing.
This is what I've often wondered.
PostgreSQL is heavily supported. But this is an app by app question. Does your specific app vendor provide your database support?
-
-
@Carnival-Boy said:
@scottalanmiller said:
Does your specific app vendor provide your database support?
No.
If not, why the concern? PostgreSQL is just as supported as any other enterprise database offering.
-
@scottalanmiller said:
@Carnival-Boy said:
@scottalanmiller said:
Does your specific app vendor provide your database support?
No.
If not, why the concern? PostgreSQL is just as supported as any other enterprise database offering.
Not with Dynamics thought, as far as I know you can only use it with MS SQL (full version, not lite).
-
Just a quick update on pricing, here is what I got from my vendor for a current quote:
SQL Server 2014 Core License: $3,322 x 2 = $6,644
or
SQL Server 2014 Standard: $823 + SQL Server 2014 User CAL: $192 x 25 = $4,800 = $5,623
They could honestly get away with only a 2 core License for their current usage, but they decided to go with 4 core license to handle growth.
-
If you go core based licensing, you probably have to go four cores any how.
i.e. if you're a VM, MS says you have to license a minimum of 4 cores.
If you're on bare metal you have to license everything in the box - I suppose you could purpose build a 2 core box and then get away with only buying two cores, but that seems wasteful.
-
So this SQL 2008 R2, never used copy that I have ready to go...It shows to be 5 CAL's, which is the exact number of Dynamics users I have. So is this acceptable to use or do I need to count our other 45 users who indirectly access SQL by spreadsheet SQL Queries? Just making sure who is counted as a CAL.
-
If a user touches SQL directly or indirectly (though an application) you need a license for them.
You'll need licensing to cover those 45 users.
-
@Dashrender said:
If a user touches SQL directly or indirectly (though an application) you need a license for them.
You'll need licensing to cover those 45 users.
Got it...I'll check on adding 45 to this one...thanks!
-
@garak0410 said:
So this SQL 2008 R2, never used copy that I have ready to go...It shows to be 5 CAL's, which is the exact number of Dynamics users I have. So is this acceptable to use or do I need to count our other 45 users who indirectly access SQL by spreadsheet SQL Queries? Just making sure who is counted as a CAL.
Yep you will, only if those Spreedsheets were completely stand-alone and have the data exported by one of the 5 users you could get away with it.
-
@garak0410 said:
@Dashrender said:
If a user touches SQL directly or indirectly (though an application) you need a license for them.
You'll need licensing to cover those 45 users.
Got it...I'll check on adding 45 to this one...thanks!
You will have to buy SQL 2014 CALS to my understanding. So the price should be similar to what I listed above.
-
@JaredBusch said:
@garak0410 said:
@Dashrender said:
If a user touches SQL directly or indirectly (though an application) you need a license for them.
You'll need licensing to cover those 45 users.
Got it...I'll check on adding 45 to this one...thanks!
You will have to buy SQL 2014 CALS to my understanding. So the price should be similar to what I listed above.
Which means that Core licensing would save you a bundle!
-
@scottalanmiller said:
@Carnival-Boy said:
@scottalanmiller said:
Does your specific app vendor provide your database support?
No.
If not, why the concern? PostgreSQL is just as supported as any other enterprise database offering.
The app vendor doesn't support the database, but they don't support the app if it is used with an unsupported database, if you follow me?
Anyway, I'm an SQL Server boy now and that isn't going to change - I've invested time and money into getting proficient so switching for the sake of saving on licencing is false economy. I haven't used Oracle for a few years now. Licencing cost is only one part of the total cost of ownership.
-
@Carnival-Boy said:
The app vendor doesn't support the database, but they don't support the app if it is used with an unsupported database, if you follow me?
I'm with ya. Wasn't sure if they did or not. Often they only care that there is a database interface. Since the database is external and elsewhere, they never see the database and all that matters is that, in this case, an Oracle interface is presented. All of their documentation and work would be done as if it were Oracle and unless they were told otherwise or given access to poke around on the database server they would have no way to know that it was not Oracle being used.
It is very surprising that they would take the time to support Oracle and not PostgreSQL. Normally you'd expect PostgreSQL to get precedence today and Oracle to be an afterthought.
-
@scottalanmiller said:
PostgreSQL to get precedence today and Oracle to be an afterthought.
Especially considering oracles prices are plain crazy. Though dynamics isn't exactly cheap.
-
@Carnival-Boy said:
Anyway, I'm an SQL Server boy now and that isn't going to change - I've invested time and money into getting proficient so switching for the sake of saving on licencing is false economy. I haven't used Oracle for a few years now. Licencing cost is only one part of the total cost of ownership.
True, but an enormous one. SQL Server licensing is very expensive and requires Windows licensing as well. And it is recurring every so many years. If you want failover or more cores over time, that licensing cost increases.
In many cases, the difference can be tens of thousands of dollars every so many years (say five.) That's not a ton, but over a decade a continuous savings of a couple thousand dollars per year plus the flexibility to do HA for free or cheap and the ability to run as many cores or users as you want and never have to manage licenses does add up.
Also makes moving to hosted solutions far easier and less expensive.
There is totally value to using what you know and SQL Server is a great product. But there is a large value is moving away too. Unlike Windows vs. Linux where the learning curve is large and the cost savings is small, with databases often the learning curve is smaller between them and the cost savings is much larger.
