![]() ![]() The database connection settings are configured in TEAMCITY_DATA_DIR\config\database.properties file. 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. Please note that TeamCity actively modifies its own database schema. Perform database-specific steps described below. The database connection settings are configured in. In short, do not EVER use internal HSQLDB database for production TeamCity instances. Please also note that our support does not cover any performance or database data loss issues if you are using the internal database. Also, internal database can become extremely slow on large data sets (say, database storage files over 200Mb). ![]() ![]() The internal database may crash and lose all your data (e.g. An external database is usually more reliable and provides better performance. However, we strongly recommend using an external database as a back-end TeamCity database in a production environment. The internal database suits evaluation purposes only it works out of the box and requires no additional setup. If you evaluated TeamCity with internal database and want to preserve the data while switching to an external database, please refer to Migrating to an External Database.īy default, TeamCity runs using an internal database based on the HSQLDB database engine. This page covers external database setup for the first use with TeamCity. See also description of what is stored where on Manual Backup and Restore page. TeamCity stores build history, users, build results and some run time data in an SQL database. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |