Move external MSSQL database
Can someone point me to documentation or best practices on how to move an external MSSQL database? I found this page on setting up the MSSQL database, which we did years ago, but the server is being retired and we need to move the database. We use 2021.2.3 and thought there might be a more guided process than taking the server offline and editing database.properies.
Please sign in to leave a comment.
Hi David,
if you are looking for some more in depth guiding, you can use this article for reference: https://www.jetbrains.com/help/teamcity/migrating-to-external-database.html . As stated there, it's usually fine just moving it and adapting the database.properties since you are just moving within a single platform (MSSQL - MSSQL), while our migration process is more geared towards different systems, mainly because it offers cross-system tooling. There isn't really anything more convoluted than that otherwise. TeamCity requires the database to work, so it needs to be taken down before moving, then the database.properties is what tells teamcity how to connect to it. The only other point that might be worth mentioning is that teamcity, being a java based application, needs a jdbc connector to use the database. Since you are moving from MSSQL to MSSQL the same connector should work, but TeamCity does not manage the connector versioning, so if you are using an old one you might want to update it as well.