Page History

...

If you evaluated TeamCity with the internal database which is not recommended for production, please refer to Migrating to an External Database.

...

1. Configure the external database to be used by TeamCity (see the database-specific sections below).
2. Run the TeamCity server for the first time.
3. Select an external database to be used and specify the database connection settings.
   If required, you can later manually modify your database connection settings.
   Note that TeamCity creates its own database schema on the first start and actively modifies it during the upgrade. The schema is not changed when TeamCity is working normally.
   The user account used by TeamCity should have permissions to create new, modify and delete existing tables in its schema, in addition to usual read/write permissions on all tables.
4. You may also need to download the JDBC driver for your database.
   

   Anchor
   database_driver database_driver

   Anchor
   Database Driver Installation Database Driver Installation

   Due to licensing terms, TeamCity does not bundle driver jars for external databases. You will need to download the Java JDBC driver and put the appropriate .jar files (see driver-specific sections below) from it into the <TeamCity Data Directory>/lib/jdbc directory.
   Please note that the .jar files should be compiled for the Java version not greater than the one used to run TeamCity, otherwise you might see "Unsupported major.minor version" errors related to the database driver classes.
   
   

...

Download the required PostgreSQL JDBC42 driver and place it into the <TeamCity Data Directory>/lib/jdbc. Proceed with the TeamCity setup.

Set the connectionProperties.autosave=conservative in the database properties file to address this issue with PostgreSQL JDBC driver.

...