ManagementStudio relies on a SQL database to access all data collected about your migration, from application usage to deployment schedules. Any issues connecting to the database could result in poor performance or, in extreme cases, being unable to use ManagementStudio.
If you're experiencing issues connecting to the database, use the information below to help to determine where the issue lies.
Check Network Connectivity
The PowerShell Test-NetConnection cmdlet is a simple way to check that one computer can communicate with another over the network. To check that the servers in the ManagementStudio solution can communicate with each other, you will need to test connectivity to:
- The ManagementStudio IIS from your machine,
- The ManagementStudio SQL server from your machine,
- The ManagementStudio SQL server from the ManagementStudio IIS server.
To start the diagnostics:
- Click Start, type PowerShell and select Windows PowerShell
- In the PowerShell window, type Test-NetConnection -Computer [servername] -Port [Port] and press the Enter key. For example:
Test-NetConnection -Computer managementstudio.local -Port 1433
A warning will be displayed if the diagnostic fails to communicate with the server over the specified port. The cause of this is typically infrastructure related (e.g. firewall or DNS).
Check Database Connectivity
To check the connectivity between the ManagementStudio IIS and the SQL server:
- Create a file on the ManagementStudio IIS host called SQLTest.udl
- Double-click the file to open the Data Link Properties window
- Enter the following details:
- The name of your SQL server and the SQL instance
- The ManagementStudio service account and password
- Select the ManagementStudio database from the drop-down
- Click the Test Connection button to verify connectivity.
Failure to connect to the database indicates a problem with the username and/or password.
If you require further support, please visit ManagementStudio's Service Desk to search the knowledge base or create a new support ticket.