jira数据库配置

Connecting JIRA to SQL Server 2008
Skip to end of metadata    
Page restrictions apply Attachments:2 Added by Andrew Lui [Atlassian Technical Writer], last edited by Rosie Jameson [Atlassian Technical Writer] on Mar 03, 2011 (view change) show comment
Go to start of metadata
Full Size These instructions will help you connect JIRA to a Microsoft SQL Server 2008 database. On this page:  1. Before you begin: 1.1 Export your existing JIRA data 1.2 Shut down JIRA     2. Configure SQL Server 3. Copy the SQL Server driver to your application server 4. Use the JIRA Configuration Tool 5. Configure the database connection manually 5.1 Configure your application server to connect to SQL Server 5.2 Configure the JIRA Entity Engine 5.3 Next steps  Installation notes
1. Before you begin:
1.1 Export your existing JIRA data
If you are already using JIRA, create an export of your data as an XML backup. You will then be able to transfer data from your old database to your new database, as described in Switching databases.
1.2 Shut down JIRA

2. Configure SQL Server
1. Create a database for JIRA to store issues in (e.g. jiradb). Note that the collation type must be case insensitive, e.g.: 'SQL_Latin1_General_CP437_CI_AI' is case insensitive. If it is using your server default, check the collation type of your server. Remember the name of this database, as it will be used again when configuring JIRA in steps 4 or 5 of this article. SQL Server uses Unicode encoding to store characters. This is sufficient to prevent any possible encoding problems. 2. Create a database user which JIRA will connect as (e.g. ( See SQL Startup Errors for details.) 3. Create an empty 'schema' in the database (e.g. jiraschema) for the JIRA tables. Please note that a 'schema' in SQL Server 2008 is a distinct namespace used to contain objects, and is different from a traditional database schema. You are not required to create any of JIRA's tables, fields or relationships (JIRA will create these objects in your empty schema when it starts for the first time). You can read more on SQL Server 2008 schemas in the relevant Microsoft documentation. 4. Ensure that the user has permission to connect to the database and create and populate tables in the newly-created schema. 5. Ensure that TCP/IP is enabled on SQL Server and listening on the correct port (the port is 1433 for the default instance of SQL Server). Read the Microsoft documentation for information on how to enable a network protocol (TCP/IP) and how to configure SQL server to listen on a specific port. 6. Ensure that SQL Server is operating in the appropriate authentication mode. By default, SQL Server operates in 'Windows Authentication Mode'. However, if your user is not associated with a trusted SQL connection, i.e. 'Microsoft SQL Server, Error: 18452' is received during JIRA startup, you will need to change the authentication mode to 'Mixed Authentication Mode'. Read the Microsoft documentation on authentication modes and changing the authentication mode to 'Mixed Authentication Mode' 7. Turn off the SET NOCOUNT option. (The JIRA on MS SQL Server document provides details on the errors that occur if SET NOCOUNT is set.) To turn off SET NOCOUNT:  Open SQL Server Management Studio and navigate to Tools -> Options -> Query Execution -> SQL Server -> Advanced. The following screenshot displays the configuration panel for this setting in MSSQL Server 2008.
jirauser ). Note that jirauser should not be the database owner, but should be in the db_owner role.