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/features-comparison.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ description: This article compares the database engine features of Azure SQL Dat
5
5
author: danimir
6
6
ms.author: danil
7
7
ms.reviewer: wiassaf, bonova, mathoma, danil
8
-
ms.date: 12/31/2024
8
+
ms.date: 03/13/2025
9
9
ms.service: azure-sql
10
10
ms.subservice: service-overview
11
11
ms.topic: conceptual
@@ -59,7 +59,7 @@ The following table lists the major features of SQL Server and provides informat
59
59
|[Cross-database transactions](/sql/relational-databases/linked-servers/linked-servers-database-engine)| No | Yes, within the instance. See [Linked server differences](../managed-instance/transact-sql-tsql-differences-sql-server.md#linked-servers) for cross-instance queries. |
60
60
|[Database mail - DbMail](/sql/relational-databases/database-mail/database-mail)| No | Yes |
61
61
|[Database mirroring](/sql/database-engine/database-mirroring/database-mirroring-sql-server) (deprecated) | No | No |
62
-
|[Database mirroring in Microsoft Fabric](/fabric/database/mirrored-database/overview)| Yes |No|
62
+
|[Database mirroring in Microsoft Fabric](/fabric/database/mirrored-database/overview)| Yes |Yes|
63
63
|[Database snapshots](/sql/relational-databases/databases/database-snapshots-sql-server)| No | No |
64
64
|[Database virtualization](../managed-instance/data-virtualization-overview.md)| No | Yes |
65
65
|[DBCC statements](/sql/t-sql/database-console-commands/dbcc-transact-sql)| Most, see individual statements | Yes, see [DBCC differences](../managed-instance/transact-sql-tsql-differences-sql-server.md#dbcc)|
Copy file name to clipboardExpand all lines: azure-sql/database/in-memory-oltp-overview.md
+11-2Lines changed: 11 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: In-memory technologies greatly improve the performance of transacti
4
4
author: WilliamDAssafMSFT
5
5
ms.author: wiassaf
6
6
ms.reviewer: mathoma
7
-
ms.date: 09/19/2024
7
+
ms.date: 03/13/2025
8
8
ms.service: azure-sql-database
9
9
ms.subservice: performance
10
10
ms.topic: concept-article
@@ -116,7 +116,7 @@ With elastic pools, the In-Memory OLTP storage is shared across all databases in
116
116
117
117
### <aid="changing-service-tiers-of-databases-that-use-in-memory-oltp-technologies"></a> Change service tiers of databases that use In-Memory OLTP technologies
118
118
119
-
In-Memory OLTP isn't supported in the General Purpose, Standard, and Basic service tiers of Azure SQL Database. Therefore, it isn't possible to scale a database that has any In-Memory OLTP objects to one of these tiers. If you want to scale a database to one of these service tiers, remove all memory-optimized tables and table types as well as all natively compiled T-SQL modules, or convert them to disk-based objects and regular T-SQL modules.
119
+
In-Memory OLTP isn't supported in the General Purpose, Standard, and Basic service tiers of Azure SQL Database. Therefore, it isn't possible to scale or [restore](#restore-a-database-with-in-memory-oltp-objects)a database that has any In-Memory OLTP objects to one of these tiers. If you want to scale a database to one of these service tiers, remove all memory-optimized tables and table types as well as all natively compiled T-SQL modules, or convert them to disk-based objects and regular T-SQL modules.
120
120
121
121
When you scale down a Business Critical or a Premium database, data in the memory-optimized tables must fit within the In-Memory OLTP storage that is available in the destination service objective of the database or elastic pool. If you try to scale down the database or elastic pool, or move a database into an elastic pool, and the destination service objective doesn't have enough available In-Memory OLTP storage, the operation fails.
122
122
@@ -138,6 +138,15 @@ SELECT * FROM sys.table_types WHERE is_memory_optimized = 1;
### Restore a database with In-Memory OLTP objects
142
+
143
+
If you created any [In-Memory OLTP](in-memory-oltp-overview.md#in-memory-oltp) objects in a database and want to [restore the database](recovery-using-backups.md), you must use the Business Critical or Premium service tiers for the restored database. This applies even if you deleted all In-Memory OLTP objects before the restore point-in-time.
144
+
145
+
To make future automatic backups of the database restorable in other service tiers after all In-Memory OLTP objects are deleted, follow this procedure:
146
+
147
+
1. Scale the database to the General Purpose, Standard, or Basic service tier.
148
+
1. If required, scale the database back to the Business Critical or Premium service tier, or to the Hyperscale service tier.
149
+
141
150
## In-memory columnstore
142
151
143
152
In-memory columnstore technology is enabling you to store and query a large amount of data in the tables. Columnstore technology uses column-based data storage format and batch query processing to achieve gain up to 10 times the query performance in OLAP workloads over traditional row-oriented storage. You can also achieve gains up to 10 times the data compression over the uncompressed data size.
Copy file name to clipboardExpand all lines: azure-sql/database/recovery-using-backups.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ description: Learn about point-in-time restore, which enables you to roll back a
5
5
author: dnethi
6
6
ms.author: dinethi
7
7
ms.reviewer: wiassaf, mathoma, danil
8
-
ms.date: 02/03/2025
8
+
ms.date: 03/13/2025
9
9
ms.service: azure-sql-database
10
10
ms.subservice: backup-restore
11
11
ms.topic: how-to
@@ -52,12 +52,12 @@ Several factors affect the recovery time to restore a database through automated
52
52
53
53
- The size of the database
54
54
- The compute size of the database
55
-
- The number of transaction logs involved
55
+
- The size of the transaction log backups involved
56
56
- The amount of activity that needs to be replayed to recover to the restore point
57
57
- The network bandwidth if the restore is to a different region
58
58
- The number of concurrent restore requests that are processed in the target region
59
59
60
-
For a large or very active database, the restore might take several hours. A prolonged outage in a region might cause a high number of geo-restore requests for disaster recovery. When there are many requests, the recovery time for individual databases can increase. For information on recovery times, see [RTO and RPO](business-continuity-high-availability-disaster-recover-hadr-overview.md?view=azuresql-db&preserve-view=true#rto-and-rpo).
60
+
For a large or very active database in the service tiers other than [Hyperscale](service-tier-hyperscale.md), the restore might take several hours. A prolonged outage in a region might cause a high number of geo-restore requests for disaster recovery. When there are many requests, the recovery time for individual databases can increase. For information on recovery times, see [RTO and RPO](business-continuity-high-availability-disaster-recover-hadr-overview.md?view=azuresql-db&preserve-view=true#rto-and-rpo).
61
61
62
62
For a single subscription, you have the following limitations on the number of concurrent restore requests. These limitations apply to any combination of point-in-time restores, geo-restores, and restores from long-term retention backup.
63
63
@@ -90,6 +90,7 @@ You generally restore a database to an earlier point for recovery purposes. You
90
90
> - You can't perform a point-in-time restore on a geo-secondary database. You can do so only on a primary database.
91
91
> - The `BackupFrequency` parameter isn't supported for Hyperscale databases.
92
92
> - Database restore operations are resource-intensive and might require a service tier of S3 or greater for the restoring (target) database. Once restore completes, the database or elastic pool might be scaled down, if required.
93
+
> - If you created any [In-Memory OLTP](in-memory-oltp-overview.md#in-memory-oltp) objects in a database in the Business Critical or Premium service tiers, then you must use the Business Critical or Premium service tiers for the restored database. For more information, see [Restore a database with In-Memory OLTP objects](in-memory-oltp-overview.md#restore-a-database-with-in-memory-oltp-objects).
Copy file name to clipboardExpand all lines: docs/includes/entra-id-tutorial.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,11 +29,14 @@ In this tutorial, you learn how to:
29
29
- The server and instance enabled by Azure Arc. For more information, see [Connect your SQL Server to Azure Arc](../sql-server/azure-arc/connect.md).
30
30
- Access to Microsoft Entra ID is available for authentication purpose. For more information, see [Microsoft Entra authentication for SQL Server](../relational-databases/security/authentication-access/azure-ad-authentication-sql-server-overview.md).
31
31
-[SQL Server Management Studio (SSMS)](../ssms/download-sql-server-management-studio-ssms.md) version 18.0 or higher is installed on the client machine. Or download the latest [Azure Data Studio](/azure-data-studio/download-azure-data-studio).
32
+
- A supported certificate.
33
+
34
+
Microsoft Entra ID supports CSP certificates. Entra ID does not support CNG certificates.
32
35
33
36
### Authentication prerequisites
34
37
35
38
> [!NOTE]
36
-
> Extended functionality has been implemented in Azure to allow the automatic creation of the Azure Key Vault certificate and Microsoft Entra application during setting up a Microsoft Entra admin for the SQL Server. For more information, see [Tutorial: Using automation to set up the Microsoft Entra admin for SQL Server](../relational-databases/security/authentication-access/azure-ad-authentication-sql-server-automation-setup-tutorial.md).
39
+
> You can use Azure to automatically create the Azure Key Vault certificate and Microsoft Entra application when you set up a Microsoft Entra admin for the server. For more information, see [Tutorial: Using automation to set up the Microsoft Entra admin for SQL Server](../relational-databases/security/authentication-access/azure-ad-authentication-sql-server-automation-setup-tutorial.md).
37
40
38
41
- Microsoft Entra application registration for SQL Server. Registering a SQL Server instance as a Microsoft Entra application allows the instance to query Microsoft Entra ID, and allows the Microsoft Entra application to authenticate on behalf of the SQL Server instance. Application registration also requires a few permissions, which are used by SQL Server for certain queries.
Copy file name to clipboardExpand all lines: docs/linux/sql-server-linux-release-notes-2022.md
+19-21Lines changed: 19 additions & 21 deletions
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 contains the release notes and supported features for
4
4
author: rwestMSFT
5
5
ms.author: randolphwest
6
6
ms.reviewer: amitkh, vanto
7
-
ms.date: 01/16/2025
7
+
ms.date: 03/13/2025
8
8
ms.service: sql
9
9
ms.subservice: linux
10
10
ms.topic: release-notes
@@ -34,38 +34,35 @@ Most existing client tools that target [!INCLUDE [ssNoVersion](../includes/ssnov
34
34
35
35
## Latest versions for all packages
36
36
37
-
This section lists the latest versions of each package per distribution, for [!INCLUDE [ssSQL22](../includes/sssql22-md.md)]. The following table shows the most recent release, which is **CU 17**. For full release history, see [Release history for [!INCLUDE [ssNoVersion](../includes/ssnoversion-md.md)] 2022](/troubleshoot/sql/linux/release-history-2022).
37
+
This section lists the latest versions of each package per distribution, for [!INCLUDE [ssSQL22](../includes/sssql22-md.md)]. The following table shows the most recent release, which is **CU 18**. For full release history, see [Release history for [!INCLUDE [ssNoVersion](../includes/ssnoversion-md.md)] 2022](/troubleshoot/sql/linux/release-history-2022).
38
38
39
39
| Version | Release | Date | Build | KB article |
40
40
| --- | --- | --- | --- | --- |
41
-
|[!INCLUDE [ssSQL22](../includes/sssql22-md.md)]| CU 17 | 2025-01-16 | 16.0.4175.1 |[Support article](/troubleshoot/sql/releases/sqlserver-2022/cumulativeupdate17)|
42
-
43
-
> [!IMPORTANT]
44
-
> The Microsoft Entra managed identity feature for SQL Server on Azure VM isn't supported on Linux. For more information, see [Improvement: Microsoft Entra managed identity support for backup and restore database operations and for EKM with AKV in SQL Server on Azure VMs](/troubleshoot/sql/releases/sqlserver-2022/microsoft-entra-managed-identity-support-for-backup-restore-database-ekm-akv).
41
+
|[!INCLUDE [ssSQL22](../includes/sssql22-md.md)]| CU 18 | 2025-03-13 | 16.0.4185.3 |[Support article](/troubleshoot/sql/releases/sqlserver-2022/cumulativeupdate18)|
45
42
46
43
- The **mssql-server-is** package isn't supported on SUSE in this release. For more information, see [SQL Server on Linux: Known issues](sql-server-linux-known-issues.md#sql-server-integration-services-ssis).
47
44
48
45
| Distribution | Package name | Package version | Download |
0 commit comments