3 ms·
I don't have an answer to the issue of getting PostgreSQL in corporate environments - but I did run into a couple other hurdles in trying. 1. It's surprisingl
by imperialWicket 14y ago
I don't have an answer to the issue of getting PostgreSQL in corporate environments - but I did run into a couple other hurdles in trying.
1. It's surprisingly difficult to find an experienced PostgreSQL DBA who wants to work in a corporate environment.
2. It's even more difficult to get a large corporation to pay a reasonable salary (why would we pay more for a PostgreSQL DBA, when we can just throw that money at Oracle/Microsoft and get a cheaper DBA with all the certs...) which might entice an experienced PostgreSQL DBA to join the organization.
- tbrownaw 14y agoI would guess that #1 is caused by #2... does #2 mean that Oracle+DBA (or MSSQL+DBA) is cheaper than a Postgres DBA, or just that the database and the DBA are generally paid for out of different department's budgets?
- imperialWicket 14y agoI think it's correct that (2) directly influences (1). And I think that most corporate groups are willing to hire an Oracle/MS SQL DBA with small amounts of experience but the carrying the right certifications. To expand a bit, IMO - that scenario doesn't really exist for PostgreSQL DBAs, you are either experienced or inexperienced (with no weight-carrying certificate to complement credentials). Hence the corporate environment won't hire an entry-level DBA who has no certs to validate the hire, and they won't justify the seemingly added cost of an experienced PostgreSQL DBA.
- sargun 14y agoRight now, it's incredibly difficult to find good PostgreSQL talent. One of those reasons is because a lot of postgres skills are interchangeable with MS-SQL, and Oracle (or insert enterprise RDBMS of choice here), and they pay much better for less complex work.