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
Copy file name to clipboardExpand all lines: azure-sql/database/high-availability-sla.md
+5-10Lines changed: 5 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -98,16 +98,11 @@ The zone-redundant version of the high availability architecture is illustrated
98
98
> For zone redundant availability, choosing a [maintenance window](./maintenance-window.md) other than the default is currently available in [select regions](./maintenance-window.md?preserve-view=true&view=azuresql#azure-region-support).
99
99
100
100
During preview, zone redundancy for SQL Managed Instance is available in the Business Critical service tier and supported in the following regions:
101
-
102
-
- Australia East
103
-
- Brazil South
104
-
- East US
105
-
- Japan East
106
-
- Korea Central
107
-
- Norway East
108
-
- South Africa North
109
-
- Sweden Central
110
-
- UAE North
101
+
| Geography | Regions supporting zone redundancy for Business Critical service tier |
102
+
|:-- |:-- |
103
+
| Europe, Middle East, Africa | North Europe, Norway East, South Africa North, Sweden Central, Switzerland North, West Europe, UAE North, UK South |
104
+
| Americas | Brazil South, Canada Central, East US, South Central US, West US 3 |
105
+
| Asia Pacific | Australia East, East Asia, India Central, Japan East, Korea Central |
111
106
112
107
## Hyperscale service tier locally redundant availability
Copy file name to clipboardExpand all lines: azure-sql/database/logins-create-manage.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,7 +42,7 @@ When a user attempts to connect to a database, they provide a user account and a
42
42
With this authentication method, the user submits a user account name and associated password to establish a connection. This password is stored in the `master` database for user accounts linked to a login or stored in the database containing the user accounts *not* linked to a login.
43
43
44
44
> [!NOTE]
45
-
> Azure SQL Database only enforces password complexity for [password policy](/sql/relational-databases/security/password-policy). For password policy in Azure SQL Managed Instance, see [Azure SQL Managed Instance frequently asked questions (FAQ)](../managed-instance/frequently-asked-questions-faq.yml#password-policy-).
45
+
> Azure SQL Database only enforces [password complexity](/sql/relational-databases/security/password-policy#password-complexity) for [password policy](/sql/relational-databases/security/password-policy). For password policy in Azure SQL Managed Instance, see [Azure SQL Managed Instance frequently asked questions (FAQ)](../managed-instance/frequently-asked-questions-faq.yml#password-policy-).
46
46
47
47
-[Azure Active Directory Authentication](authentication-aad-overview.md)
Copy file name to clipboardExpand all lines: azure-sql/database/service-tier-hyperscale.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: This article describes the Hyperscale service tier in the vCore-bas
4
4
author: dimitri-furman
5
5
ms.author: dfurman
6
6
ms.reviewer: wiassaf, mathoma
7
-
ms.date: 11/29/2022
7
+
ms.date: 1/24/2023
8
8
ms.service: sql-database
9
9
ms.subservice: service-overview
10
10
ms.topic: conceptual
@@ -165,6 +165,8 @@ These are the current limitations of the Hyperscale service tier. We're activel
165
165
| Database integrity check | DBCC CHECKDB isn't currently supported for Hyperscale databases. DBCC CHECKTABLE ('TableName') WITH TABLOCK and DBCC CHECKFILEGROUP WITH TABLOCK may be used as a workaround. See [Data Integrity in Azure SQL Database](https://azure.microsoft.com/blog/data-integrity-in-azure-sql-database/) for details on data integrity management in Azure SQL Database. |
166
166
| Elastic Jobs | Using a Hyperscale database as the Job database isn't supported. However, elastic jobs can target Hyperscale databases in the same way as any other database in Azure SQL Database. |
167
167
|Data Sync| Using a Hyperscale database as a Hub or Sync Metadata database isn't supported. However, a Hyperscale database can be a member database in a Data Sync topology. |
168
+
| Hyperscale service tier premium-series hardware (preview) | Zone redundancy is currently not supported for premium-series and memory optimized premium-series hardware.|
169
+
| Hyperscale service tier premium-series hardware (preview) | Azure SQL Database maintenance window is currently not supported for premium-series and memory optimized premium-series. |
| Mac | .zip |[Universal](https://go.microsoft.com/fwlink/?linkid=2222873) [Intel CPU](https://go.microsoft.com/fwlink/?linkid=2222874) [Apple Silicon](https://go.microsoft.com/fwlink/?linkid=2222680)|
42
42
43
43
If you have comments or suggestions or want to report a problem with downloading Azure Data Studio, submit an issue to our team on the [Azure Data Studio feedback page](https://github.com/microsoft/azuredatastudio/issues/).
@@ -4,7 +4,7 @@ description: This article has release notes for Azure Data Studio.
4
4
author: erinstellato-ms
5
5
ms.author: erinstellato
6
6
ms.reviewer: maghan, randolphwest
7
-
ms.date: 01/16/2023
7
+
ms.date: 01/25/2023
8
8
ms.service: azure-data-studio
9
9
ms.topic: conceptual
10
10
ms.custom:
@@ -20,18 +20,74 @@ This article provides details about updates, improvements, and bug fixes for the
20
20
21
21
:::image type="icon" source="../includes/media/download.svg" border="false"::: **[Download and install the latest release!](./download-azure-data-studio.md)**
22
22
23
-
### November 2022 (hotfix 2)
23
+
### January 2023
24
24
25
-
Azure Data Studio 1.40.2 is the latest general availability (GA) release.
25
+
Azure Data Studio 1.41.0 is the latest general availability (GA) release.
26
26
27
-
- Release number: 1.40.2
28
-
- Release date: December 27, 2022
27
+
- Release number: 1.41.0
28
+
- Release date: January 25, 2023
29
29
30
-
#### Bug fixes in 1.40.2
30
+
#### What's new in 1.41.0
31
31
32
32
| New Item | Details |
33
33
| --- | --- |
34
-
| Terminal | Fixed a security vulnerability that allowed an .exe to be easily run by a user. |
| Azure SQL Migration Extension | Premium series memory optimized SQL MI SKUs included in recommendations. |
36
+
| Connection | Migrated Azure authentication library from ADAL to MSAL. MSAL is the library used by default starting with release 1.41. However, if you encounter issues, you can change back to ADAL within **Settings > Azure: Authentication Library**. |
37
+
| Connection | Added ability to provide a description when creating a firewall rule from Azure Data Studio. |
38
+
| Connection | Include ability to change password for new or expired login. |
39
+
| Connection | Add support for SQL Server Alias use when connecting to a server. |
40
+
| MongoDB Atlas Extension | Provides the ability to connect to and query data on MongoDB Atlas (Preview). |
41
+
| Notebooks | Provide option for users to convert markdown to a table or not when HMTL table tag is present. |
42
+
| Object Explorer | Databases are no longer brought online in serverless Azure SQL when Databases node is expanded. |
43
+
| Object Explorer | Added support for Ledger views. |
44
+
| Query Editor | Fixes and updates to SQL grammar (colorization and auto-complete). |
45
+
| Query Plan Viewer | Changed default folder to be user’s home directory when saving a query plan. |
46
+
| Query Results | Added ability to only copy Column Headers, and only for cells that are highlighted. |
47
+
| Query Results | Added option to show or hide the action bar in the results window. |
48
+
| Query Results | Increased height of horizontal scrollbar in results window. |
49
+
| Query Results | Added new aggregate details in the results toolbar when selecting multiple cells. |
50
+
| SQL Projects Extension | Provide the ability select an existing project via a new dropdown. |
51
+
52
+
#### Bug fixes in 1.41.0
53
+
54
+
| New Item | Details |
55
+
| --- | --- |
56
+
| Accessibility | Accessibility improvements were made in the Query Plan Viewer, Query History Extension and Migration Extension. |
57
+
| Big Data Cluster | Fix missing connect icon in BDC view header bar. |
58
+
| Big Data Cluster | Fixed issue preventing HDFS nodes for BDC servers in Object Explorer from expanding. |
59
+
| Connection | Added ability to delete a connection that has expired AAD credentials. |
60
+
| Connection | Improved experience when Azure Active Directory token expiration occurs. |
61
+
| Connection | Improved connection experience when using multiple Azure tenants. |
62
+
| Connection | Addressed problem with adding a firewall exception for a non-default Azure subscription. |
63
+
| Migration Extension | Added support for non-public clouds for migration scenarios. |
64
+
| MySQL Extension | Updated resource endpoints to support AAD logins in the MySQL extension. |
65
+
| Notebooks | Improve Intellisense refresh in Notebook cells. |
66
+
| Notebooks | Address issue with "New Notebook Job" resulting in an empty form. |
67
+
| Object Explorer | Fixed issue with database list not loading. |
68
+
| Object Explorer | Fixed issue with key binding for objectExplorer.manage not working. |
69
+
| Query Execution | Fixed error generated when executing a query with LEFT JOIN and NULL values. |
70
+
| Query Plan Viewer | When saving query plans (.sqlplan file), the filename will numerically increment to prevent duplicate filenames. |
71
+
| Query Results | Fixed issue where users were unable to open JSON data as a new file. |
72
+
| Query Results | Provide proper cell selection and navigation in the query results grid. |
73
+
| Query Results | Improved the handling of line breaks when copying cell contents. |
74
+
| Query Results | Addressed issue where a column would re-size incorrectly when auto-sizing in the results output. |
| Query Results | Fixed behavior where focus was incorrectly set on a cell using keyboard navigation. |
77
+
| Resource Deployment | Remove 'Preview' flag for SQL Server 2022 deployment types. |
78
+
| Schema Compare Extension | Fixed problem where differences in schema compare were not being highlighted. |
79
+
| Schema Compare Extension | Permissions are now included in schema compare when the "Include Permissions" option is selected. |
80
+
| SQL Projects Extension | Changes to db_datawriter or db_datareader roles are now supported. |
81
+
| SQL Projects Extension | Updated Database Projects Net Core SDK Location dialog to be more descriptive. |
82
+
| Table Designer | Updated Table Designer to disable transaction support for Azure Synapse databases. |
83
+
| Table Designer | Addressed problem of the table name not refreshing after being updated prior to publishing. |
84
+
| Table Designer | Fixed issue where table designer could not be opened for existing Ledger tables. |
85
+
86
+
For a full list of bug fixes addressed for the January 2023 release, visit the [bugs and issues list on GitHub](https://github.com/microsoft/azuredatastudio/milestone/92?closed=1).
87
+
88
+
#### Known issues in 1.41.0
89
+
90
+
For a list of the current known issues, visit the [issues list on GitHub](https://github.com/microsoft/azuredatastudio/issues?q=is%3Aissue).
35
91
36
92
## Azure Data Studio feedback
37
93
@@ -41,7 +97,7 @@ You can reference [Azure Data Studio feedback](https://github.com/microsoft/azur
41
97
42
98
| Azure Data Studio release | Build number | Release date | Hotfix |
43
99
| --- | --- | --- | --- |
44
-
|[November 2022](#november-2022)| 1.40.0 | November 16, 2022 |[hotfix](#november-2022-hotfix)|
|[August 2022](#august-2022)| 1.39.1 | August 30, 2022 |[hotfix](#august-2022-hotfix)|
46
102
|[August 2022](#august-2022)| 1.39.0 | August 24, 2022 | N/A |
47
103
|[July 2022](#july-2022)| 1.38.0 | July 27, 2022 | N/A |
@@ -86,9 +142,18 @@ You can reference [Azure Data Studio feedback](https://github.com/microsoft/azur
86
142
> [!NOTE]
87
143
> All previous versions of Azure Data Studio are not supported.
88
144
89
-
### November 2022 (hotfix)
145
+
### November 2022 (hotfix 2)
146
+
147
+
- Release number: 1.40.2
148
+
- Release date: December 27, 2022
149
+
150
+
#### Bug fixes in 1.40.2
90
151
91
-
Azure Data Studio 1.40.1 is the latest general availability (GA) release.
152
+
| New Item | Details |
153
+
| --- | --- |
154
+
| Terminal | Fixed a security vulnerability that allowed an .exe to be easily run by a user. |
155
+
156
+
### November 2022 (hotfix)
92
157
93
158
- Release number: 1.40.1
94
159
- Release date: November 23, 2022
@@ -101,12 +166,10 @@ Azure Data Studio 1.40.1 is the latest general availability (GA) release.
101
166
102
167
### November 2022
103
168
104
-
Azure Data Studio 1.40 is the latest general availability (GA) release.
105
-
106
169
- Release number: 1.40
107
170
- Release date: November 16, 2022
108
171
109
-
#### What's new in 1.40
172
+
#### What's new in 1.40.0
110
173
111
174
| New Item | Details |
112
175
| --- | --- |
@@ -135,7 +198,7 @@ Azure Data Studio 1.40 is the latest general availability (GA) release.
135
198
| VS Code merge | VS Code merges to version 1.67. Read [their release notes](https://code.visualstudio.com/updates/v1_67) to learn more. |
136
199
| SQL Database Projects | Adds SQL projects support for syntax introduced in SQL Server 2022. |
137
200
138
-
#### Bug fixes in 1.40
201
+
#### Bug fixes in 1.40.0
139
202
140
203
| New Item | Details |
141
204
| --- | --- |
@@ -153,6 +216,12 @@ Azure Data Studio 1.40 is the latest general availability (GA) release.
153
216
| SQL Projects | Fixed bug in SQL Projects that led to extension not using output path when publishing a project. |
154
217
| SQL Projects | Fixed bug that caused .NET install to not be found when using the SQL Projects extension on Linux platforms. |
155
218
219
+
For a full list of bug fixes addressed for the November 2022 release, visit the [bugs and issues list on GitHub](https://github.com/microsoft/azuredatastudio/milestone/91?closed=1).
220
+
221
+
#### Known issues in 1.40.0
222
+
223
+
For a list of the current known issues, visit the [issues list on GitHub](https://github.com/microsoft/azuredatastudio/issues?q=is%3Aissue).
224
+
156
225
### August 2022 (hotfix)
157
226
158
227
- Release number: 1.39.1
@@ -201,8 +270,17 @@ Azure Data Studio 1.40 is the latest general availability (GA) release.
201
270
| Notebooks | Fixed a bug that prevented markdown cell toolbar shortcuts from working after creating a new split view cell. |
202
271
| Notebooks | Fixed a bug that caused text cells to be erroneously created in split view mode when the notebook default text edit mode was set to "Markdown". |
203
272
273
+
For a full list of bug fixes addressed for the August 2022 release, visit the [bugs and issues list on GitHub](https://github.com/microsoft/azuredatastudio/milestone/87?closed=1).
274
+
275
+
#### Known issues in 1.39.0
276
+
277
+
For a list of the current known issues, visit the [issues list on GitHub](https://github.com/microsoft/azuredatastudio/issues?q=is%3Aissue).
278
+
204
279
### July 2022
205
280
281
+
- Release number: 1.38.0
282
+
- Release date: July 27, 2022
283
+
206
284
### What's new in 1.38.0
207
285
208
286
| New Item | Details |
@@ -233,8 +311,17 @@ Azure Data Studio 1.40 is the latest general availability (GA) release.
233
311
| Notebooks | Fixed issue where notebook wasn't opening if a cell contains an unsupported output type. |
234
312
| Schema Compare | Fixed issue where views and stored procedures weren't correctly recognized by schema compare after applying changes. |
235
313
314
+
For a full list of bug fixes addressed for the July 2022 release, visit the [bugs and issues list on GitHub](https://github.com/microsoft/azuredatastudio/milestone/90?closed=1).
315
+
316
+
#### Known issues in 1.38.0
317
+
318
+
For a list of the current known issues, visit the [issues list on GitHub](https://github.com/microsoft/azuredatastudio/issues?q=is%3Aissue).
319
+
236
320
### June 2022
237
321
322
+
- Release number: 1.37.0
323
+
- Release date: June 15, 2022
324
+
238
325
### What's new in 1.37.0
239
326
240
327
| New Item | Details |
@@ -260,6 +347,12 @@ Azure Data Studio 1.40 is the latest general availability (GA) release.
260
347
| Notebooks | Fixed inconsistencies with notebook cell behavior and toolbars. |
261
348
| Notebooks | Fixed issues with keyboard navigation. |
262
349
350
+
For a full list of bug fixes addressed for the June 2022 release, visit the [bugs and issues list on GitHub](https://github.com/microsoft/azuredatastudio/milestone/85?closed=1).
351
+
352
+
#### Known issues in 1.37.0
353
+
354
+
For a list of the current known issues, visit the [issues list on GitHub](https://github.com/microsoft/azuredatastudio/issues?q=is%3Aissue).
Copy file name to clipboardExpand all lines: docs/relational-databases/security/encryption/setup-steps-for-extensible-key-management-using-the-azure-key-vault.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -296,6 +296,8 @@ You can generate four types of keys in an Azure key vault that will work with SQ
296
296
> [!IMPORTANT]
297
297
> For the SQL Server Connector, use only the characters a-z, A-Z, 0-9, and hyphens (-), with a 26-character limit.
298
298
> Different key versions under the same key name in an Azure key vault don't work with the [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Connector. To rotate an Azure key vault key that's being used by [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)], see the Key Rollover steps in the "A. Maintenance Instructions for [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Connector" section of [SQL Server Connector Maintenance & Troubleshooting](../../../relational-databases/security/encryption/sql-server-connector-maintenance-troubleshooting.md).
299
+
>
300
+
> When rotating versions of the key, do not disable the version originally used to encrypt the database. SQL Server will be unable to recover the database (it will be in a 'recovery pending' state) and may generate a 'Crypto Exception' memory dump until the old version is enabled.
0 commit comments