Database Server Requirements
Go Up to Main Page
Supported Database Platforms
Team Server and Repository databases may run on any of the following database platforms:
- Microsoft SQL Server 2012 to 2019.
- Microsoft SQL Server Express Edition 2012 to 2017 is supported, but should be used only for product trials and proof of concepts.
- Oracle 11g, 12c R2, 18c, 19c.
In order for the Repository to communicate with the database, the machine running Team Server must also have the corresponding RDBMS client utility installed.
- Install the 64-bit version of Oracle Client Utilities.
- Configure your server in one of the Oracle configuration tools:
- Net Easy Config
- Net Configuration Assistant
- Create a connection alias.
- If you are upgrading using Oracle, increase the number of processes (connections) to 200 before running.
- Minimum permissions for owner of Repository and Team Server schema:
- CREATE INDEXTYPE
- CREATE PROCEDURE
- CREATE SEQUENCE
- CREATE SESSION
- CREATE SYNONYM
- CREATE TABLE
- CREATE TRIGGER
- CREATE TYPE
- CREATE VIEW
- UNLIMITED TABLESPACE
Microsoft SQL Server Characteristics
- 64-bit client libraries are already installed on Windows machines.
- Ensure that the server and database are set to case-insensitive, as case-sensitive is not supported. Also set the SQL Server Configuration Properties to allow SQL Server authentication. Team Server only supports SQL Server Authentication.
- The database and server collation must be set to SQL_Latin1_General_CP1_CI_AS
- When using SQL Server, ensure the SQL Server Agent is running.
- Team Server on SQL Server only supports the following communication protocols:
- Shared Memory
- Named Pipes
- The option ANSI_NULLS (Server Properties > Connections) needs to be set as On.
- The default schema for Team Server database needs to be dbo. If you were using a different schema please move the tables to dbo schema previous to install or upgrade Team Server.
Note: After configuring a new installation against a SQL Server 2014 or later database, it is recommended that you go into the properties of the new database and change the compatibility settings to 2012 or 2008. This step helps prevent significant performance degradation in many environments. For more information about this feature, see an IDERA forum post about this subject.