Setting up SQL Server databases

Perforce does not provide support for installing, configuring, or maintaining SQL Server. A qualified SQL Server database administrator should install and configure the database.

Keep the following in mind:

• Do not add, delete, or modify any fields in the Helix ALM tables.
• Do not directly add, edit, or delete any data in the tables.
• Do not create different primary keys. This will adversely affect application performance.
• Do not create complex triggers on any of the tables. Triggers may cause severe database issues and correcting these issues is not covered by Perforce.
• Create a process to back up database tables on a regular schedule.

• Running SQL Server and the Helix ALM Server on the same computer can result in slow performance if not configured correctly. Make sure SQL Server is configured correctly to avoid using all the system memory.

Note:  You must be a member of the db_ddladmin role and have the CREATE TABLE, CREATE PROCEDURE, and CREATE VIEW permissions to create the Helix ALM tables.

Connecting to SQL Server

The only supported method for using SQL Server is via ODBC. After creating the database to use for the Helix ALM product, add a SQL Server data source name (DSN) on the Helix ALM computer. The server database and each database used to host Helix ALM projects must have a unique DSN. See Creating DSNs for SQL Server Databases for information.

Creating server database tables

The Helix ALM Server automatically creates tables when you start the server or convert the server database. The TTServerDB.sql script file, which is located in the SQLServer directory in the Helix ALM application directory, is used to create the tables.