Edit

Share via


Known issues in SQL Server Management Studio

Applies to: SQL Server Azure SQL Database Azure SQL Managed Instance Azure Synapse Analytics

This page lists known issues for SQL Server Management Studio 21.

Feature Details Workaround
Arm64 SSMS isn't currently supported on Arm64. Run SSMS on a device that isn't Arm64.
Designers The JSON data type isn't available for columns when creating or editing a table in Table Designer. See SSMS 21.0 Preview 2.0 - Table Designer missing the "json" datatype. Use T-SQL to add columns with the JSON data type, this functionality is planned for a later release.
Designers Unable to use SSMS after closing the New View pane when the Add Table dialog is left open. See SSMS 21 Preview 1: New View window "Add Table" not aware I closed out of New View. Close the Add Table dialog before closing the view pane.
Extended Events The Specify Data Storage page is truncated in the Extended Events Wizard. See Extended Events Wizard is cut off on Specify Data Storage page. Use the New Session... option to create an Extended Events session.
Integration Services There's currently no support for Integration Services in SQL Server Management Studio 21. Use SSMS 20.2 to connect to Integration Services.
Logins Unable to map a credential for a login. See SSMS v21 Preview 1 - Bug in Login Properties for Credentials. Use T-SQL to map a login to a credential.
Maintenance Plans There's currently no support for creating or editing maintenance plans in SQL Server Management Studio 21. Use SSMS 20.2 to create or edit maintenance plans.
Menu Opening a folder from File > Recent Projects and Solutions generates one of the following errors: "System.InvalidOperationException: Can't enqueue project dependencies calculation before starting solution load" or "An exception of type NullReferenceException has been encountered." if opening the folder also opens one or more files that were open in the editor when the folder was last closed. Closing the error allows work to continue. Alternatively, close all files in the editor before closing a folder.
Modern Connection Dialog (Preview) There's currently no way to create a firewall rule when connecting to an Azure SQL DB with the Modern connection dialog (Preview). Create a firewall rule in the Azure Portal or switch back to the Classic connection dialog.
Modern Connection Dialog (Preview) Trying to change the password for a newly created SQL login with the MUST_CHANGE property enabled generates the error "Login failed for user. Reason: The password of the account must be changed. (Microsoft SQL Server, Error: 18488)". See Instead of Change password dialog an error pops up. Use the Classic connection dialog to change the password.
Modern Connection Dialog (Preview) Importing connection history for the new connection dialog generates the error "An error occurred while importing the connection history from the classic connection dialog. The given key was not present in the dictionary." The error occurs when you have corrupted connections in your history, and they aren't imported into the new dialog. The error can be safely ignored.
Modern Connection Dialog (Preview) Upon first use, when importing saved connections to the Modern connection dialog (Preview), saved passwords are lost. Manually enter your passwords to save them to your connection profiles in the Modern connection dialog (Preview).
Options Enabling Per Monitor Awareness (PMA) by checking Optimize rendering for screens with different pixel densities (requires restart) within Tools > Options can cause issues with dialogs not rendering. Don't enable Optimize rendering for screens with different pixel densities (requires restart) within Tools > Options.
Options Enabling Unified Settings Experience (requires restart) within Tools > Options > General > Preview Features can cause issues with dialogs not rendering. Don't enable Unified Settings Experience (requires restart) within Tools > Options > General > Preview Features.
Query Store When you use any of the Query Store reports, the Replica dropdown list menu option might not populate with the correct replica name when the Query Store for readable secondaries is enabled. Use Transact-SQL to query the Query Store data for a readable secondary where the replica_group_I'd for a secondary can be mapped using the sys.query_store_runtime_stats system catalog view, which has a foreign key relationship with the sys.query_store_replicas system catalog view.
Results Grid When you switch themes, if Results Grid is set to Results to Text, the Results component doesn't switch themes, it applies the theme SSMS uses when it originally opens. To apply any theme changes to the Results component, restart SSMS.