Skip to end of metadata
Go to start of metadata

Only applicable to the BiZZdesign on-premise solution.

Making changes to the Team Server database configuration can be needed if want to you install a new version of SQL or want to migrate the SQL Server to another machine. The Team Server needs to be reconfigured to look for the new SQL Server. It is important that the Team Server connects to the correct database. But changing the configuration can also be done if you want to expand the Team Server with optional settings like a lock time-out and maximum lifetime of a connection.

The Team Server database configuration can be changed in the application.conf configuration file. This file is located in the TeamServerHome/conf folder of your Team Server installation.

Changing the database configuration should only be done by application administrators who are familiar with installing and configuring software and databases.


  1. Stop and uninstall the Team Server.

    If the Team Server runs as a service, stop the service and uninstall it using the uninstallservice.bat file (default location is TeamServerHome/bat folder).

    If the Team Server runs via runConsole.bat, you can simply terminate it via the command box.

  2. Make a backup of the current SQL database and the application.conf file.

  3. Open the application.conf file with a text editor, and edit the settings you need to change.

    Application settings

    Here you can change the teamservice URL. This is usually your server name. Only change the URL if you are relocating the Team Server.

    Configure database connection
    Here you can change the database connection settings, for example, to switch from SQL authentication to integrated security, or reconfigure the jdbc URL to link to a new SQL Team Server.

    Optional settings
    These settings can only be configured for SQL Server. The following optional settings are available. The Team Server is preconfigured with default settings. You should only change them if you experience issues.

    lockTimeout: Set the number of milliseconds to wait before the database reports a lock time-out
    maxLifetime: The maximum lifetime of a connection, in minutes. 
    maximumPoolSizeIf the default number of active connections is not sufficient, change the number of connections. Set the maximum total of active connections that can be allocated from the pool at the same time. 
    connectionTimeout: Set the maximum number of seconds that the pool will wait (when there are no available connections) for a connection to be returned before throwing an exception.

  4. Save the changes, and test the new settings by restarting the Team Server and then opening the server location in your web browser.

  5. If the changes are OK, reinstall the Team Server service and run it from the service list, or restart the Team Server via the runConsole.bat.