Hello,
I am having an issue getting Jira service desk connected to Microsoft SQL. I have SQL running on the same server as Jira. I have run through the setup wizard on the site however i am not having luck. The error i get is...
Jira - Jira setup
Error connecting to database
Login failed for user 'jira'. ClientConnectionId:3ca7ed60-f568-4a7e-9f50-98e3bb055036
I have given the user name jira rights to connect and owner of the db
I have also tried with windows authentication with a domain admin that has owner rights to the db as well but no luck.
Any Idea's what could be causing this?
THank You
Nick
Hi Nick,
Just to confirm, there is a specific setup required for the user in Jira
Specifically:
Create a database user which Jira will connect as (e.g.
jiradbuser
). This user should not be the database owner, but should be in thedb_owner
role.
Can you review the article that pertains to your SQL version and confirm? Be advised that this is specifically for MS SQL Server, but not the Express versions.
Regards,
Shannon
Hey Shannon,
I am exempting to set this up on SQL 2017 Express. Is there a way to set this up on that version?
Thank You,
Nick
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Nick,
SQL Server 2017 is not supported in Jira, nor are any of the Express versions.
Have a look at Supported Platforms for more information:
Microsoft SQL Server:
Jira will not work on:
- Express Editions of Microsoft SQL Server
Supported Microsoft SQL databases use the Microsoft JDBC 6.2.1 Driver.
Supported versions are:
Support for SQL Server 2017 is in progress on this feature request:
I can say that I have heard of users setting up Jira successfully on SQL Server Express versions, but it can cause many performance issues, so I don't recommend it.
If you don't want to commit to the full version of SQL, I would recommend setting up Jira using Postgres or MySQL which are free and supported.
Let me know if you have any questions!
Shannon
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Looks like i got it to work on SQL 2017. Next step is getting this to be on SSL. How would i be able to do that?
Thank You,
Nick
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Nick,
Thank you for confirming that. Feel free to let us know here what you did to fix it, in case other users want to try using SQL Express 2017 in the future.
Keep in mind as well if your performance gets too bad, please consider moving to a supported database.
For the SSL, I would recommend starting with the following article:
If you get stuck, please raise a new question on Community so we can help you there.
Regards,
Shannon
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.