You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| Connection | Added icons to the Query Editor status bar to indicate the encryption method used for the connection. |
54
56
| Connection | Added Microsoft Entra ID authentication to **New Login** wizard. |
55
57
| Drivers | Updated Microsoft.Data.SqlClient version to 5.1.4, which includes support for Strict encryption and Transport Layer Security (TLS) 1.3. |
56
-
| Libraries | Updated Server Management Objects (SMO) version to 171.30.0|
58
+
| Libraries | Updated Server Management Objects (SMO) version to 171.30.0|
57
59
| Libraries | Updated DacFx version to 162.1.x. |
58
60
| Options | Introduced a new option, **Trust server certificate for imported connections**, in **Tools > Options > SQL Server Object Explorer > Commands** under **Connection security**. For more information, see [Options (SQL Server Object Explorer - Commands)](menu-help/options-sql-server-object-explorer-commands.md). |
59
61
@@ -85,7 +87,7 @@ Available languages:
85
87
| Replication | If Azure SQL Managed Instance is the publisher and SSMS is running on a machine that isn't in the same virtual network as the publisher, you aren't able to insert a tracer token via Replication Monitor. | To insert tracer tokens, use Replication Monitor in SSMS on a machine that is in the same virtual network as the Azure SQL Managed Instance publisher. |
86
88
| Stretch Database | Removed Stretch Database Wizard. | Use T-SQL to configure Stretch Database or use SSMS 18.9.1 or earlier to use the Stretch Database Wizard. |
87
89
88
-
#### Known issues using Strict encryption 20.0
90
+
#### Known issues using Strict Encryption in 20.0
89
91
90
92
| Feature | Details | Workaround |
91
93
| --- | --- | --- |
@@ -105,14 +107,16 @@ You can reference [SQL user feedback](https://aka.ms/ssms-feedback) for other kn
105
107
Download previous SSMS versions by selecting the download link in the related section.
106
108
107
109
| SSMS version | Build number | Release date |
108
-
| ------------| ------------|------------ |
110
+
| --- | --- | --- |
109
111
|[19.3](#193)| 19.3.4.0 | January 10, 2024 |
110
112
|[18.12.1](#18121)| 15.0.18420.0 | June 21, 2022 |
111
113
|[17.9.1](#1791)| 14.0.17289.0 | November 21, 2018 |
112
114
|[16.5.3](#1653)| 13.0.16106.4 | January 30, 2017 |
@@ -122,36 +126,36 @@ Download previous SSMS versions by selecting the download link in the related se
122
126
#### What's new in 19.3
123
127
124
128
| Feature | Details |
125
-
| ----------|------- |
129
+
| --- | --- |
126
130
| Azure Data Studio installation integration | The installation of SSMS installs Azure Data Studio 1.47.1. |
127
131
128
132
#### Bug fixes in 19.3
129
133
130
134
| Feature | Details |
131
-
| --------|------- |
135
+
| --- | --- |
132
136
| Accessibility | Addressed issue with screen reader announcing incomplete or incorrect information in the database properties dialog. |
133
137
| Always Encrypted | Fixed inability to change the **Enable Secure Enclaves** option when creating a new Azure SQL Database using a non-English installation of SSMS. |
134
138
| Availability Groups | Changed text color for primary server name in the Availability Group Dashboard, which caused the entry to appear empty. |
135
139
| Extended Events | Changed text color for data column after selecting **View Target Data** for the ring_buffer target. |
136
-
| Installer | Fixed issue where users may be prompted to update SQL Server Management Studio even if the current release is installed, see [Bug in 19.2.56.2 update version detection](https://feedback.azure.com/d365community/idea/bb5e60b9-5d85-ee11-a81c-002248544521). |
140
+
| Installer | Fixed issue where users might be prompted to update SQL Server Management Studio even if the current release is installed, see [Bug in 19.2.56.2 update version detection](https://feedback.azure.com/d365community/idea/bb5e60b9-5d85-ee11-a81c-002248544521). |
137
141
| Object Explorer | Resolved crash occurring when trying to close Object Explorer while the tree is still expanding. |
138
-
| Reports | Updated Server Dashboard report to correctly show the number of schedulers when more than 255 are available, see [SSMS 19.2 - Reports - Server dashboard - Processors used by instance - wrong number](https://feedback.azure.com/d365community/idea/cdf3d393-a689-ee11-a81c-6045bdb7ea56). |
142
+
| Reports | Updated Server Dashboard report to correctly show the number of schedulers when more than 255 are available, see [SSMS 19.2 - Reports - Server dashboard - Processors used by instance - wrong number](https://feedback.azure.com/d365community/idea/cdf3d393-a689-ee11-a81c-6045bdb7ea56). |
139
143
| Security | Update to [Microsoft.Data.SqlClient 3.1.5](https://github.com/dotnet/SqlClient/blob/main/release-notes/3.1/3.1.5.md) to address [CVE-2024-0056](https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-0056). |
140
144
141
145
#### Known issues 19.3
142
146
143
147
| Feature | Details | Workaround |
144
-
| --------| -------|---------- |
145
-
| Analysis Services | When you connect to Analysis Services with Microsoft Entra MFA, if you add a new role or open properties for a role, the message “the identity of the user being added to the role is not fetched properly” appears. | This error is benign and can be ignored. It will be addressed within the Azure infrastructure soon, and no updates to SSMS are required. |
148
+
| --- | --- | --- |
149
+
| Analysis Services | When you connect to Analysis Services with Microsoft Entra MFA, if you add a new role or open properties for a role, the message "the identity of the user being added to the role is not fetched properly" appears. | This error is benign and can be ignored. It will be addressed within the Azure infrastructure soon, and no updates to SSMS are required. |
146
150
| Analysis Services | After adding a new role, or when opening properties for an existing role, you can't use **Search by name or email address** to add a user. | A user can be added with the **Manual Entry** option. |
147
151
| Database Designer | Selecting the Design option for a view that references a table using spatial data causes SSMS to crash. | Use T-SQL to make changes to the view. |
148
152
| Database Mirroring | When you launch the Database Mirroring Monitor from the mirrored node, the primary node isn't listed. | Use SSMS 18.12.1 if you need to monitor mirroring from the mirrored node. |
149
153
| General SSMS | Import settings from SSMS 17 option not available. | Settings can be imported from SSMS 18. |
150
-
| Link feature for Azure SQL Managed Instance | After you remove an existing mirroring endpoint certificate on SQL Server, link creation through the wizard might fail due to unestablished trust between SQL Server and Azure SQL Managed Instance, even though all checks are successful. | Use PowerShell command ``Get-AzSqlInstanceServerTrustCertificate`` to check whether SQL Server mirroring endpoint certificate named "<SQL_Server_Instance_Name>" exists in the Azure SQL Managed Instance. If so, use PowerShell command ``Remove-AzSqlInstanceServerTrustCertificate`` to remove it before a new link creation attempt. |
151
-
| Linked servers | Creating a linked server to Azure SQL Database with SQL Server selected as Server type connects to the master database. | To create a linked server to Azure SQL Database, select **Other data source** for the **Server type**, and select **Microsoft OLE DB Provider for SQL Server** or **Microsoft OLE DB Driver for SQL Server** as the **Provider**. Enter logical server name in the Data source field, and enter database name in the Catalog field. |
154
+
| Link feature for Azure SQL Managed Instance | After you remove an existing mirroring endpoint certificate on SQL Server, link creation through the wizard might fail due to unestablished trust between SQL Server and Azure SQL Managed Instance, even though all checks are successful. | Use PowerShell command `Get-AzSqlInstanceServerTrustCertificate` to check whether SQL Server mirroring endpoint certificate named "<SQL_Server_Instance_Name>" exists in the Azure SQL Managed Instance. If so, use PowerShell command `Remove-AzSqlInstanceServerTrustCertificate` to remove it before a new link creation attempt. |
155
+
| Linked servers | Creating a linked server to Azure SQL Database with SQL Server selected as Server type connects to the `master` database. | To create a linked server to Azure SQL Database, select **Other data source** for the **Server type**, and select **Microsoft OLE DB Provider for SQL Server** or **Microsoft OLE DB Driver for SQL Server** as the **Provider**. Enter logical server name in the Data source field, and enter database name in the Catalog field. |
152
156
| PolyBase | PolyBase node isn't visible in Object Explorer when connecting to SQL 2022. | Use SSMS 18.12.1. |
153
157
| Profiler | The Profiler menu isn't localized. | No current alternative. |
154
-
| Replication | If Azure SQL Managed Instance is the publisher and SSMS is running on a machine, which isn't in the same vNet as the publisher, you are not able to insert a tracer token via Replication Monitor. | To insert tracer tokens, use Replication Monitor in SSMS on a machine that is in the same vNet as the Azure SQL Managed Instance publisher. |
158
+
| Replication | If Azure SQL Managed Instance is the publisher and SSMS is running on a machine, which isn't in the same virtual network as the publisher, you aren't able to insert a tracer token via Replication Monitor. | To insert tracer tokens, use Replication Monitor in SSMS on a machine that is in the same virtual network as the Azure SQL Managed Instance publisher. |
155
159
| Stretch DB | Removed Stretch DB Wizard. | Use T-SQL to configure Stretch DB or use SSMS 18.9.1 or earlier to use the Stretch DB Wizard. |
156
160
157
161
### 18.12.1
@@ -167,13 +171,13 @@ Download previous SSMS versions by selecting the download link in the related se
167
171
#### What's new in 18.12.1
168
172
169
173
| New Item | Details |
170
-
| --------|------- |
174
+
| --- | --- |
171
175
| Azure Data Studio installation integration | Installation of SSMS installs Azure Data Studio 1.37. |
172
176
173
177
#### Bug fixes in 18.12.1
174
178
175
179
| New Item | Details |
176
-
| --------|------- |
180
+
| --- | --- |
177
181
| Always Encrypted | Fixed issue with Column Master Key creation generating an exception when using Azure Key Vault as the key store. |
178
182
| Data Classification | Fixed issue with "Couldn't load file or assembly 'Microsoft.Information.Protection', Version=1.10.98.0" after upgrading to SSMS 18.10 or higher. See [Latest SSMS 18.11.1 breaks the Data Classification. Get missing assembly error after updating](https://feedback.azure.com/d365community/idea/af89d5d7-45a4-ec11-a81c-0022484ee92d). |
179
183
| SSMS General | Resolved error related to dacpac deployment using the Deploy Data-tier application option in Azure SQL DB with MFA. |
@@ -203,25 +207,29 @@ SQL Server utility is no longer available in versions 17.x and newer.
203
207
204
208
#### Uninstall and reinstall SSMS 17.x
205
209
206
-
If your SSMS installation is having problems, and a standard uninstall and reinstall doesn't resolve them, you can first try [repairing](https://support.microsoft.com/help/4028054/windows-10-repair-or-remove-programs) the Visual Studio 2015 IsoShell. If repairing the Visual Studio 2015 IsoShell doesn't resolve the problem, the following steps have been found to fix many random issues:
210
+
If your SSMS installation is having problems, and a standard uninstall and reinstall doesn't resolve them, you can first try [repairing](https://support.microsoft.com/help/4028054/) the Visual Studio 2015 IsoShell. If repairing the Visual Studio 2015 IsoShell doesn't resolve the problem, the following steps have been found to fix many random issues:
207
211
208
212
1. Uninstall SSMS the same way you uninstall any application (using **Add or remove programs**).
209
213
210
214
1. Uninstall Visual Studio 2015 IsoShell **from an elevated cmd prompt**:
1. Uninstall Microsoft Visual C++ 2015 Redistributable the same way you uninstall any application. Uninstall both x86 and x64 if they're on your computer.
216
222
217
223
1. Reinstall Visual Studio 2015 IsoShell **from an elevated cmd prompt**:
1. Upgrade to the [latest version of the Visual C++ 2015 Redistributable](https://support.microsoft.com/help/2977003/the-latest-supported-visual-c-downloads) if you're not currently up to date.
232
+
1. Upgrade to the [latest version of the Visual C++ 2015 Redistributable](/cpp/windows/latest-supported-vc-redist) if you're not currently up to date.
225
233
226
234
### 16.5.3
227
235
@@ -239,34 +247,34 @@ If your SSMS installation is having problems, and a standard uninstall and reins
239
247
240
248
- Users can deploy SQL Server Integration Services (SSIS) packages containing OData Connection Manager, which connects to a Microsoft Dynamics AX/CRM Online resource to the SSIS catalog. For more information, For details, see [OData Connection Manager](../integration-services/connection-manager/odata-connection-manager.md).
241
249
242
-
- Configuring Always Encrypted on an existing table fails with errors on unrelated objects.[Connect ID 3103181](https://connect.microsoft.com/SQLServer/feedback/details/3103181/setting-up-always-encrypted-on-an-existing-table-fails-with-errors-on-unrelated-objects)
250
+
- Configuring Always Encrypted on an existing table fails with errors on unrelated objects.
243
251
244
-
- Configuring Always Encrypted for an existing database with multiple schemas doesn't work.[Connect ID 3109591](https://connect.microsoft.com/SQLServer/feedback/details/3109591/sql-server-2016-always-encrypted-against-existing-database-with-multiple-schemas-doesnt-work)
252
+
- Configuring Always Encrypted for an existing database with multiple schemas doesn't work.
245
253
246
-
- The Always Encrypted, Encrypted Column wizard fails due to the database containing views that reference system views.[Connect ID 3111925](https://connect.microsoft.com/SQLServer/feedback/details/3111925/sql-server-2016-always-encrypted-encrypted-column-wizard-failed-task-failed-due-to-following-error-cannot-save-package-to-file-the-model-has-build-blocking-errors)
254
+
- The Always Encrypted, Encrypted Column wizard fails due to the database containing views that reference system views.
247
255
248
256
- When you encrypt with Always Encrypted, errors from refreshing modules after encryption are incorrectly handled.
249
257
250
-
-*Open recent* menu doesn't show recently saved files.[Connect ID 3113288](https://connect.microsoft.com/SQLServer/feedback/details/3113288/ssms-2016-open-recent-menu-doesnt-show-recently-saved-files)
258
+
-*Open recent* menu doesn't show recently saved files.
251
259
252
-
- SSMS is slow when right-clicking an index for a table (over a remote (Internet) connection).[Connect ID 3114074](https://connect.microsoft.com/SQLServer/feedback/details/3114074/ssms-slow-when-right-clicking-an-index-for-a-table-over-a-remote-internet-connection)
260
+
- SSMS is slow when right-clicking an index for a table (over a remote (Internet) connection).
253
261
254
-
- Fixed an issue with the SQL Designer scrollbar.[Connect ID 3114856](https://connect.microsoft.com/SQLServer/feedback/details/3114856/bug-in-scrollbar-on-sql-desginer-in-ssms-2016)
262
+
- Fixed an issue with the SQL Designer scrollbar.
255
263
256
264
- Context menu for tables momentarily stops responding.
257
265
258
-
- SSMS occasionally throws exceptions in Activity Monitor and crashes.[Connect ID 697527](https://connect.microsoft.com/SQLServer/feedback/details/697527/).
266
+
- SSMS occasionally throws exceptions in Activity Monitor and crashes.
259
267
260
-
- SSMS 2016 crashes with the error "The process was terminated due to an internal error in the .NET Runtime at IP 71AF8579 (71AE0000) with exit code 80131506".
268
+
- SSMS crashes with the error: "The process was terminated due to an internal error in the .NET Runtime at IP 71AF8579 (71AE0000) with exit code 80131506."
261
269
262
-
## Additional Downloads
270
+
## More downloads
263
271
264
272
For a list of all SQL Server Management Studio downloads, search the [Microsoft Download Center](https://www.microsoft.com/download/search.aspx?q=sql%20server%20management%20studio&p=0&r=10&t=&s=Relevancy~Descending).
265
273
266
274
For the latest release of SQL Server Management Studio, see [Download SQL Server Management Studio (SSMS)](download-sql-server-management-studio-ssms.md).
0 commit comments