Icon

You are viewing the documentation of TeamCity 2018.x, which is not the most recently released version of TeamCity.
View this page in the latest documentation or refer to the listing to choose the documentation corresponding to your TeamCity version.

 

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Create a new database. As the primary collation, use the case-sensitive collation (collation name ending with '_CS_AS') corresponding to your locale.
  2. Create a TeamCity user and ensure that this user is the owner of the database (grant the user dbo rights), which will give the user the ability to modify the database schema.
    For SSL connections, ensure that the version of MS SQL server and the TeamCity version of java are compatible. We recommend using the latest update of SQL server.
  3. Allocate sufficient transaction log space depending on how intensively the server will be used. The recommended setup is not less then 1Gb.
  4. Make sure SQL Server Browser is running.
  5. Make sure TCP/IP protocol is enabled for SQL Server instance.Make sure that the "no count"  setting is disabled: the enabled "no count" setting prevents TeamCity from starting queued builds. 

On TeamCity server side (with MS SQL)

...