Please propose the best database engine for running a JIRA/Confluence instance.
I found an issue here: https://jira.atlassian.com/browse/CONF-12465
At the bottom, Charles Miller wrote that the best solution is the one for which we have experience.
It's quite old post so do you still stand by this opinion?
Maybe from your experience with different customers, you recommend specific engine?
We are considering MSSQL and PostgreSQL. Do you know any advantages/disadvantages between them?
Atlassian recommend PostGreSQL first and MySQL second.
I'd never recommend MSSQL over those two, or even Oracle to be frank, especially for java based tools. I've never had database problems with Post or My with Atlassian products, but MSSQL has turned out to be an absolutely monumental pain in the neck, repeatedly.
However, Charles' advice is good. My experience is based on not really having DBA expertise on hand. You may need it if you use MSSQL. You almost certainly won't need it for day-to-day usage if you use Post or My (barring doing the standard backups/failover stuff). If you have expert MSSQL people on hand, and you are comfortable with MSSQL, and not with the others, then use it.
I'd agree with Nic and take PostgreSQL & Oracle over MS-SQL. If MS-SQL is what you know then it can work but don't ever be tempted to use the MS JDBC drivers. Atlassian warn you off them for a reason. Unfortunately, it means you loose the ability to do any kind of failover but that 0.1% of uptime wasn't worth the 99.9% of degraded performance.
Go with your strengths and if you know PostgreSQL then your question has been answered!
It's poorly supported by MS as well - when I first ran into problems with it, MS support told us to try their drivers instead of the jtds ones. The MS drivers do not work - they feel like they haven't been tested, just thrown out there to pretend that MS supports java.
That said, it can work fine. It does work fine in a lot of cases. But don't bet on it.
Oracle. The answers here haven't changed in the last 3 years. The preferred order is very much Postgres first, MySQL a close second, Oracle third, and Microsoft in a very distant fourth place. The only time I'd recommend MS-SQL is when your organisation has no support expertise for the others.
Yes, that's a bug on the Atlassian side. But the fact that Microsoft's own drivers are unusable is the rather telling point here. The advice still stands - you should prefer the use one of the better databases unless you have no support for them in your organisation.
TLDR; If you can afford it: Train a db admin on postgres and use postgres. Otherwise live with the problems that you have with the other databases. I have a horrible confluence upgrade. Atassians requires you to use very specific settings for MSSQL and our DB used with confluence did not comply to them. So no in place upgrade. XML Export, new DB on th cluster and then import, then update. turned out this did not work, update failed on db checks. In the end, and with atlassian support approving it, we did it this way: xml export, change DB to Porstgres, do update, xml export change db back to MSSQL do import.... And now I fear the next update... Using MSSQL because no postgres admin available. But missing the speed and the ease that postgres gave me for updating the company wiki.
Supported Platforms macOS Windows We recently introduced support for additional hosting services such as GitHub Enterprise, GitLab (Cloud, Community Edition, Enterprise Edition), and...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs