The best answer I can give to this is:
If I have complete free-range on which one to choose for JIRA, I would put the supported four in this order:
Ok, given your comment above, MySQL is probably the best for you, so the specifics on that are:
Be careful to get the collation and locale right before you do anything with JIRA (follow the recommendations in the setup document to the letter. But take the advice of your DBAs on anything that is not covered in that doc)
Watch out for users trying to be "clever" with emojis and graphics - importing emojis and other stuff into MySQL does not work. You'll be fine with most data though.
Couldn't thank you yesterday because "limit on no of comments" as I just registered. Thanks for explanation and suggestions. In our infrastructure we have mysql clusters but with strict mode off. But I see Atlassian recommending to use with strict mode. What kind of issues I might face with out strict mode using mysql.
If you run into a bug that affects a write cycle, with strict mode off, it's more likely to allow broken data to go into the database. This is a very rare occurrence though, and does require that a bug is hit at a low level. I think the strict mode checking is a strong recommendation rather than an absolute requirement
Which database is best option for Jira?
Without a doubt, although this is not an option in your list, the recommended database would be PostgreSQL. This is the database that we at Atlassian also use for JIRA Cloud instances. This recommendation is only included in the latest supported platforms page with a complete explanation as to why we recommend this: https://confluence.atlassian.com/display/adminjiraserver071/Supported+Platforms#Supportedplatforms-postgresnote
hello, is depend if you have db or not.
for example, i use in 3 different companies the 3 db.
mysql is cheap, but have some limitations. is open Source Database. take care with the support if you have any issue.
MSSQL is expensive but not expensive than Oracle and you pay attention with the cost of the DBA. Its not so simple to find good and cheap Oracle DBA and MSSQL DBA.
The best are MSSQL and ORACLE, both are the same level for our usability. and both have a good performance and scalebility, redundance, etc.
The more important is the people support you have to admin the db. and pay attention with the cost of the licence (MSSql and Oracle).
if you are a begginer i recommend to start with MSSQL then if you grow, you can migrate.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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