TABLE OF CONTENTS

• Overview
• Warning
• Prerequistites
• Process
• Further Support

Overview

This article covers the key steps required to migrate the SQL database for ManagementStudio to a new host

Warning

You should not move a database from one server to another without checking the Collation of both servers. If they are different, you will no longer be able to Update ManagementStudio! See this article Issue: Fixing Collation issues when moving the SQL Database

Prerequistites

• Ensure that the SQL Server version used on the new host is same version or later than the current SQL server
• You will need SQL Server Management Studio with access to the ManagementStudio database
• You will need an account with full SQL privileges for making backups, restoring databases etc on both the current SQL server and the new one
• You will need access to the ManagementStudio web server with local admin privileges

Process

1. Ask all users to close ManagementStudio client
2. Stop the ManagementStudio IIS website
3. Take a full backup of the ManagementStudio database
4. Restore the database backup to the new database server ensuring the database name remains the same
5. The ManagementStudio support team will take a backup of the appsetting.json file on the IIS server
6. The appsettings.json file on the IIS server will need modifying to point to the new database server. This should be undertaken by the ManagementStudio support staff
7. A new licence will be generated by the ManagementStudio support team
8. This completes the database move.
9. Open the ManagementStudio client and logon. Test that it is functioning as expected.
10. The old database can be detached from the old SQL server to ensure that this is no longer accessible
11. Inform the users that ManagementStudio is available for general use

Further Support

If you require further support, please visit ManagementStudio's Service Desk to search the knowledge base or create a new support ticket.