- You can't write off or expense three martini lunches and golf excursions with a PostgreSQL sales rep.
- When you deal with unavailability, you can't point to the PostgreSQL support SLA's four hour response and tell your boss "not our problem".
- It's harder to justify larger budgets for your IT fiefdom and thus your sense of self-importance when you don't pay for unnecessary license fees.
Budgets have similar incentives that make teams want to keep a large budget around even if they could get the job done with less resources. That slush money comes in handy to have the vendor do all sorts of work that isn't really about getting their system running ( i.e. doing all the integration with other parts of your stack )
I think lots of open source products or smaller teams think winning those "Enterprise" deals is about having the better product and checking some boxes on a requirements sheet. When you get into enterprise its all about the relationships
That's one of the Oracle features supported by EnterpriseDB’s proprietary downstream version.
> When you deal with unavailability, you can't point to the PostgreSQL support SLA's four hour response and tell your boss "not our problem".
Also, this, but it is a 24 hour resolution window for Severity 1 issues.
> It's harder to justify larger budgets for your IT fiefdom and thus your sense of self-importance when you don't pay for unnecessary license fees.
EnterpriseDB addresses this, but certainly doesn't usually match Oracle in the budget impact department.
Maybe having clustered indexes, good partitioning, etc.
Still, I’m hard pressed to ever recommend anything other than PostgreSQL or MySQL.
Regarding support, there's plenty of fantastic companies providing support and consulting services for PostgreSQL and having used plenty of commercial databases I know of know no other database that has as vibrant a community providing amazing free support as well.
However from my experience with Oracle and from what I've heard about their source code, its fundamentals are just disgusting. Decades of haphazardly piled-up features and fixes means that if you're the lucky customer to find a new bug, good luck understanding what the heck is going on by yourself.
I'd like to think MSSQL is in a bit better shape, but they have lots of the same incentives so who knows.
> It takes 6 months to a year (sometimes two years!) to develop a single small feature (say something like adding a new mode of authentication like support for AD authentication).
There's no way in the world I would have imagined that adding AD authentication to any database would be a "single small feature".
An ass to drag onto the carpet. In enterprise speak, "support" means "legal liability". You have to be able to sue someone if it fails and loses your company money. This was taught to me by an old IT hand back when I was a young naïve Linux kiddie "you have to be able todrag somebody's ass onto the carpet when the shit breaks".
Oh yes, and there's also brand recognition and a large pool of certified Oracle or SQL Server DBAs to draw from when making hiring decisions. Yes, technical people will know that Postgres is solid and will know how to spot good people to maintain a Postgres installation -- but the person signing off on the IT budget is a total normie. He will smile when he sees familiar names and make a lolwut face when he sees postgres.
Relatedly, Postgres doesn't have a yacht. Oracle's yacht won the America's Cup.
It means that anyone in the company can ring a vendor 24/7 and get the best quality help on the product. It means your outages are smaller and less frequent. You usually can’t get that with a generic open source product or from smaller companies and it’s especially an issue issue in non-US countries where it’s often impossible to get decent support.
I’ve never once seen a company sue a vendor or vice versa.
The first three results I got from a search engine:
1. https://palisadecompliance.com/oracle-lawsuit-pushing-cloud/
2. https://www.theregister.co.uk/2018/03/22/oracle_shoddy_servi...
3. https://www.businessinsider.in/I-felt-like-we-were-being-ext...
And if you can’t handle this I think you have bigger problems to worry about.
What a retarded position to hold.
You have forgotten what the purpose of these providers was in the first place.
"Company X provides service/software Y so you can do business"
But that's not what they do.
"Company X optimizes to extract as much rent as possible from its client in order to show ever increasing amounts of profitability to the stock market"
And I’m guessing you’ve never dealt with a vendor before because often companies negotiate better terms than list price.
And CIO/CTOs rarely unilaterally make decisions on technology choices. You have Enterprise Architects for that.
In contrast, I recently heard about a company with a market cap in the tens of billions where the execs said, "By date X, we won't own hardware or run datacenters anymore." I'm told it forced a lot of teams to reevaluate fundamental technology decisions made decades ago.
So sure, the decisions are proximately about compatibility or specific features. But I think it's reasonable to ask why those specific features are necessary. Because places like Google and Facebook make it clear that it's not scale alone that makes it necessary to give Oracle a truck of cash every year.