-
Type:
Suggestion
-
Resolution: Invalid
-
Component/s: None
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Our team manages deployments for all our cloud customers. As such, I'm marking this request for improved platform support as invalid.
We have a related Jira Server ticket for this issue, see linked issues and watch that for updates on our Jira Server and Data Center products here.
Thanks!
Steve King
Product Manager
Problem Definition
During the database configuration setup, if the user configured JIRA to use a database user with Default Database configured on MSSQL server, JIRA will not know that on the MSSQL server side, it's actually using the Default Database of the user.
For example:
- JIRA DB configuration:
- <url>jdbc:jtds:sqlserver://10.60.3.37:1433;instance=SQLEXPRESS/MOG</url>.
- <username>moga</username>.
- In the SQL Server, I do not have any MOG database.
- In the SQL Server also, I have set the DB user moga configured MOGA1 as the Default Database.
- During the installation, JIRA did not complain that the database does not exist.
- After setting up JIRA, the MOGA1 database which was empty, now it has all the JIRA tables and data.
Which means, despite the database does not exist, JIRA will use the DB user's Default Database even though in the dbconfig.xml file is pointing to another database.
Suggested Solution
Documentation update:
By default, the Default Database for DB users will be master. The documentation on Connecting JIRA to SQL Server will need an update to highlight that users should not alter the Default Database value for any DB users.
- is related to
-
JRASERVER-63742 Documentation update on SQL Server connection
- Closed
- relates to
-
JRACLOUD-63741 JIRA is using the DB user's default database
- Closed