Also curious, what made you decide not to use PostgreSQL (or EnterpriseDB if you need entreprise solution)? Was it a technical reason or are you more comfortable with MS solutions in general?
I am asking because I have mostly used MySQL (pre-Oracle) and now PostgreSQL, and have always wondered what made people choose either Oracle or SQL Server. I have met both in different jobs - I hate Oracle with passion because of their licensins shenanigans, and wasn't impressed by SQL Server (though that might be in part that I was using it with SharePoint, which was... something).
You can use this to get a very ballpark idea:
https://wintelguy.com/mssql-ent-licensing-calc.pl
From actual quotes at full price, we'd be paying around the same to Microsoft for SQL Server Enterprise than we were paying Oracle BEFORE the price hike/license changes. However that doesn't include discounts which most organizations running any Microsoft software at all would be eligible for.
So in other words: Almost always cheaper than Oracle Database. Varies between a little cheaper and substantially cheaper. Both companies are trying to drag you towards Cloud however, so there's deeper discounts there right now (it's a trap!).
> Also curious, what made you decide not to use PostgreSQL (or EnterpriseDB if you need entreprise solution)?
No one person decided. This is a large organization that moves slowly and is fairly conservative. Plus the costs of migration are high, if migration fails people in management will suffer (either to their career or just outright be transferred/fired).
So in other words "nobody gets fired for buying Microsoft" or w/e. It certainly doesn't hurt that it is much easier to hire/contract in SQL Server talent than PostgreSQL. Technical considerations play a part, but only up to the point where it has to have what we need.
> I am asking because I have mostly used MySQL (pre-Oracle) and now PostgreSQL, and have always wondered what made people choose either Oracle or SQL Server.
That's because you're considering what is best using logic, reason, and technical facts. In the enterprise space more often than not major companies just follow the crowd, with a handful of trailblazers setting the standard. Oracle and SQL Server are popular because they're already popular, in a fully circular way.
If I started a business tomorrow I'd use PostgreSQL. But if I was a C-level in an enterprise and my career is on the line, I am going to be sticking with SQL Server.
The alignment between product support and product builder is muddier for c-levels to follow.
Keep in mind that MSSQL enterprise comes with a lot of tools beyond just a RDBMS. That was always the hangup when I have tried to move companies from MSSQL to something like PG.
I built and managed a data warehouse/internal reporting system for a fairly large telecom. I used ~100 ETL packages built in SSIS to pull in data from systems all over the company, SSAS to process the data and SSRS to build reports. It worked pretty well at the time 10+ years ago.
If you license all the physical cores you can run as many copies of SQL Server as your infrastructure will allow.
If you want to run SQL Server as a partial part of a private cloud then licensing per virtual core could be a significant savings in some circumstances. This is because physical cores used for other things won't require a license.
This article has more info:
https://blogs.flexera.com/elo/2017/06/an-introduction-to-mic...
If anything, I've seen a lot of non-programmers disguised as Java programmers. Armies of them in enterprise teams. A truckload of expense for not much gain.
I'm not saying it's everywhere like that of course. I've met brilliant Java developers when I contracted for SAP.
So how do you deal with such a risk?
If I had to hire I'd search programmers of less popular languages -- and only 3-5 of them. These people tend to be insanely productive and have very good perspective and culture.
I guess the day has come to make use of this feature.
Oracle used to charge us per physical core on our production nodes, with a discount for development and backup/spare.
Then suddenly they changed how it was licensed and our bill jumped up 4x (we're talking a six figure increase).
We negotiated it down somewhat (closer to a 2.5x increase as a "goodwill discount"), but since then have been quietly making changes to the code-base to make a future SQL Server migration easier. We have four years left in this contract, and we hope to be ready by then.
We're on Oracle at all because we used to use their application development suite (ADF, Forms, etc), but those all either got discontinued or turn so sour you don't want to be using them, so now Oracle DB is just a remnant.