Issue Summary

It'd be helpful to have all Database variables affecting Jira's DB connection for troubleshooting purposes.

Some features may require a certain variable — or require a variable to not be set — and we'd need a way to confirm exactly what variables are at play on Jira's DB connections.

The connection URL or properties in dbconfig.xml may cause different variables to be present and the DBA team may not easily trace them down (or not easily reproduce the connection environment when connecting through DB Client apps).

Goal

The goal of this Feature Request is to allow an easier way to troubleshoot DB connections by listing somewhere the actual active variables and configs in play for the Jira's DB connections.

It may not be trivial to reproduce the exact way Jira's connecting to the DB and what variables/configs it's loading. Connecting through a DB UI client may not load the same variables/configs Jira's loading when connecting through it's configured DB driver and dbconfig.xml params.

Workaround

Currently, we have to rely on 3rd party (paid) apps that allow DB commands to be executed through Jira's Admin UI or some Java DB connecting ad-hoc app with connection parameters copied from Jira's dbconfig.xml.

For ad-hoc troubleshooting Evaluation licenses of such apps may suffice, but still it's something we could attain with this feature implemented.

Suggestion brainstorming

• Have the DB variables present on Admin GUI
• Have the DB variables on Support Zips
• Have the DB variables on startup logs

Database example commands

PostgreSQL

...

MySQL

SHOW VARIABLES;

SHOW SESSION VARIABLES;
SELECT @@SESSION.sql_mode;

SHOW GLOBAL VARIABLES;
SELECT @@GLOBAL.sql_mode;

Oracle DB

...

SQL Server

...