Database Troubleshooting for SQL Server
On this page:
Supported Version of SQL Server
Ensure that your version of SQL Server is supported for the version of Confluence you're installing or upgrading to. See the Supported Platforms page for more information about your specific version:
Support for SQL Server versions:
- SQL Server 2014: Supported from Confluence 5.7 onwards
- SQL Server 2012: Supported from Confluence 5.2 onwards
- SQL Server 2008/2008 R2: Supported from Confluence 3.4 to Confluence 5.8
While it's possible that an older version of Confluence will work in a newer version of SQL Server, we recommend matching versions wherever possible.
Case-Sensitive Collation Requirement
When installing or upgrading Confluence, a case sensitive collation is required. Earlier versions of Confluence do not enforce this requirement, but newer versions do (from 5.5.3 onwards). You should ensure that your database has the correct collation. See Database Setup for SQL Server for more information. If you're converting an existing database to use the correct collation, see our guide on adjusting the collation of a SQL Server Database.
Setting up Authentication Mode of the SQL Server
During a login process to SQL server or while setting up your DB connection through the Setup Wizard, the following error may appear:
Login failed for user 'username'. The user is not associated with a trusted SQL Server connection. (Microsoft SQL Server, Error: 18452).
The cause of this error is that the SQL server has been configured to operate in 'Windows Authentication Mode (Windows Authentication)' and doesn't allow the use of SQL accounts.
In order to resolve this problem, change the Authentication Mode of the SQL server from 'Windows Authentication Mode (Windows Authentication)' to 'Mixed Mode (Windows Authentication and SQL Server Authentication)'.
Please refer to this Microsoft documentation for more details.
Moving from one SQL server to another
By default, Confluence uses and expects the dbo schema is assigned to the Confluence user. If you are migrating from one SQL Server database to another, it is important to ensure that the default schema of the Confluence database user matches the schema used to store Confluence data.