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/reservations-discount-overview.md
+3-6Lines changed: 3 additions & 6 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 how to buy Azure SQL Database and SQL Managed Instance reserv
5
5
author: rajeshsetlem
6
6
ms.author: rsetlem
7
7
ms.reviewer: wiassaf, mathoma
8
-
ms.date: 06/19/2025
8
+
ms.date: 12/01/2025
9
9
ms.service: azure-sql
10
10
ms.subservice: service-overview
11
11
ms.topic: how-to
@@ -65,10 +65,7 @@ When you enable zone-redundancy, resources are made available in multiple availa
65
65
66
66
Compute costs for the following zone-redundant resources include an extra charge for the zone-redundancy add-on, which is billed separately from standard compute:
67
67
-[Azure SQL Database](high-availability-sla-local-zone-redundancy.md#general-purpose-service-tier): Databases and elastic pools in the General Purpose service tier.
68
-
-[Azure SQL Managed Instance](../managed-instance/high-availability-sla-local-zone-redundancy.md#business-critical-service-tier-1): Instances in the Business Critical service tier.
69
-
70
-
> [!NOTE]
71
-
> June 2025 introduces a discount for the zone redundancy add-on for Azure SQL Managed Instance.
68
+
-[Azure SQL Managed Instance](../managed-instance/high-availability-sla-local-zone-redundancy.md#high-availability-through-zone-redundancy): Instances in the General Purpose and Business Critical service tiers.
72
69
73
70
74
71
Reservations can cover compute costs for both standard compute and the zone-redundancy add-on, but they need to be purchased as two separate reservation types:
@@ -105,7 +102,7 @@ Carefully evaluate your compute needs and reservation strategy to optimize costs
105
102
|Region |The Azure region that's covered by the reservation.|
106
103
|Deployment Type|The SQL resource type that you want to buy the reservation for.|
107
104
|Performance Tier|The service tier for the databases or managed instances. |
108
-
|Type| The reservation type. Select **vCore** for standard compute or **vCore ZR** for the [zone redundancy add-on](#reservations-for-zone-redundant-resources). The **vCore ZR** reservation type is currently only available for the Azure SQL Database General Purpose service tier and Azure SQL Managed Instance Business Critical service tier. |
105
+
|Type| The reservation type. Select **vCore** for standard compute or **vCore ZR** for the [zone redundancy add-on](#reservations-for-zone-redundant-resources). The **vCore ZR** reservation type is currently only available for the Azure SQL Database General Purpose service tier and both Azure SQL Managed Instance General Purpose and Business Critical service tiers. |
109
106
|Term |One year or three years.|
110
107
|Quantity |The number of vCores in the selected Azure region and service tier covered by the reservation. For example, if you run, or plan to run, multiple databases with a total compute capacity of standard-series (Gen5) 16 vCores in the East US region, then specify the quantity as 16 vCores to maximize the benefit for all the databases. |
Copy file name to clipboardExpand all lines: azure-sql/managed-instance/doc-changes-updates-release-notes-whats-new.md
+2-1Lines changed: 2 additions & 1 deletion
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 the new features and documentation improvements for Azu
5
5
author: MashaMSFT
6
6
ms.author: mathoma
7
7
ms.reviewer: wiassaf, mathoma
8
-
ms.date: 11/18/2025
8
+
ms.date: 12/01/2025
9
9
ms.service: azure-sql-managed-instance
10
10
ms.subservice: service-overview
11
11
ms.topic: whats-new
@@ -82,6 +82,7 @@ Learn about significant changes to the Azure SQL Managed Instance documentation.
82
82
|**Regular expression functions preview**| Regular expression (REGEX) functions return text based on values in a search pattern. Regular expression (REGEX) functions are now generally available for Azure SQL Managed Instance. For more information, see [Regular expressions](/sql/relational-databases/regular-expressions/overview) or [General Availability Announcement: Regex Support in SQL Server 2025 & Azure SQL](https://devblogs.microsoft.com/azure-sql/general-availability-announcement-regex-support-in-sql-server-2025-azure-sql/). |
83
83
|**Flexible memory GA**| Save on cost by choosing the memory allocation for your [Next-gen General Purpose](service-tiers-next-gen-general-purpose-use.md) instance based on your workload needs. This capability is now generally available. To learn more, review [Flexible memory](resource-limits.md#flexible-memory). |
84
84
|**Next-gen General Purpose GA**| An architectural upgrade of the General Purpose service tier that uses [Elastic SAN storage](/azure/storage/elastic-san/elastic-san-introduction) for greater resource flexibility, and improved performance while maintaining the same baseline cost as the General Purpose service tier. This upgrade to the service tier is now generally available (GA). To learn more, review [Next-gen General Purpose](service-tiers-next-gen-general-purpose-use.md).|
85
+
|**Zone redundancy add-on for GP**| To help save on cost, the zone redundancy reservation add-on is now available for Azure SQL Managed Instance in the General Purpose service tier. To learn more, review [zone redundancy reservation add-on](../database/reservations-discount-overview.md#reservations-for-zone-redundant-resources). |
Copy file name to clipboardExpand all lines: azure-sql/managed-instance/update-policy.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
@@ -119,7 +119,7 @@ To change the update policy for an existing instance in the Azure portal, follow
119
119
120
120
:::image type="content" source="media/update-policy/update-policy-existing-instance.md.png" alt-text="Screenshot of the SQL Managed Instance page in the Azure portal, with update policy selected.":::
121
121
122
-
1. Select **Yes** on the **Confirm update policy change** popup to save your changes. Once the **Always-up-to-date** update policy is enabled, the **SQL Server 2022** update policy is no longer available
122
+
1. Select **Yes** on the **Confirm update policy change** popup to save your changes. Once the **Always-up-to-date** update policy is enabled, the **SQL Server 2022** update policy is no longer available.
Copy file name to clipboardExpand all lines: docs/database-engine/configure-windows/configure-sql-server-encryption.md
+4-2Lines changed: 4 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: This article describes how to configure a SQL Server instance to en
4
4
author: VanMSFT
5
5
ms.author: vanto
6
6
ms.reviewer: sureshka, randolphwest
7
-
ms.date: 08/26/2025
7
+
ms.date: 11/20/2025
8
8
ms.service: sql
9
9
ms.subservice: configuration
10
10
ms.topic: how-to
@@ -192,7 +192,9 @@ The SQL Server service loads the server certificate in the following order of pr
192
192
To learn more, see [Certificate requirements for SQL Server](certificate-requirements.md).
193
193
194
194
> [!NOTE]
195
-
> SQL Server Configuration Manager only displays certificates imported through the registry if the thumbprint in the registry is an exact match for the thumbprint of the certificate, including case sensitivity. If the thumbprint doesn't match the case exactly, the certificate isn't displayed in SQL Server Configuration Manager, but the certificate is still loaded and used by SQL Server.
195
+
> Starting with SQL Server 2022 CU22 and SQL Server 2025, the thumbprint of the certificate is no longer case sensitive. In versions prior to SQL Server 2022 CU22 and SQL Server 2025, SQL Server Configuration Manager only displays certificates imported through the registry if the thumbprint in the registry is an exact match for the thumbprint, including case sensitivity. If the thumbprint doesn't match the case exactly, the certificate isn't displayed in SQL Server Configuration Manager, but the certificate is still loaded and used by SQL Server.
[!INCLUDE [SQL Server Azure SQL Database Azure SQL Managed Instance](../../includes/applies-to-version/sql-asdb-asdbmi.md)]
25
26
26
-
Contains a row per full-text index of a tabular object.
27
+
Contains a row per full-text index of a tabular object.
28
+
29
+
| Column name | Data type | Description |
30
+
| --- | --- | --- |
31
+
|`object_id`|**int**| ID of the object to which this full-text index belongs. |
32
+
|`unique_index_id`|**int**| ID of the corresponding unique, non-full-text index that is used to relate the full-text index to the rows. |
33
+
|`index_version`|**int**| Version of full-text filter and wordbreaker components that are used to populate and query this index. If you perform an in-place upgrade from [!INCLUDE [sql-server-2022](../../includes/sssql22-md.md)] and earlier versions to [!INCLUDE [sql-server-2025](../../includes/sssql25-md.md)] and later versions, existing indexes are assigned `index_version = 1`. This value is controlled by the [FULLTEXT_INDEX_VERSION](../../t-sql/statements/alter-database-scoped-configuration-transact-sql.md#fulltext_index_version) database scoped configuration option.<br /><br />**Applies to**: [!INCLUDE [sql-server-2025](../../includes/sssql25-md.md)] and later versions. |
34
+
|`fulltext_catalog_id`|**int**| ID of the full-text catalog in which the full-text index resides. |
35
+
|`is_enabled`|**bit**|`1` = Full-text index is currently enabled. |
36
+
|`change_tracking_state`|**char(1)**| State of change-tracking.<br /><br />`M` = Manual<br />`A` = Auto<br />`O` = Off |
37
+
|`change_tracking_state_desc`|**nvarchar(60)**| Description of the state of change-tracking.<br /><br />`MANUAL`<br />`AUTO`<br />`OFF`|
38
+
|`has_crawl_completed`|**bit**| Last crawl (population) that the full-text index has completed. |
39
+
|`crawl_type`|**char(1)**| Type of the current or last crawl.<br /><br />`F` = Full crawl<br />`I` = Incremental, timestamp-based crawl<br />`U` = Update crawl, based on notifications<br />`P` = Full crawl is paused. |
40
+
|`crawl_type_desc`|**nvarchar(60)**| Description of the current or last crawl type.<br /><br />`FULL_CRAWL`<br />`INCREMENTAL_CRAWL`<br />`UPDATE_CRAWL`<br />`PAUSED_FULL_CRAWL`|
41
+
|`crawl_start_date`|**datetime**| Start of the current or last crawl.<br /><br />`NULL` = None. |
42
+
|`crawl_end_date`|**datetime**| End of the current or last crawl.<br /><br />`NULL` = None. |
43
+
|`incremental_timestamp`|**binary(8)**| Timestamp value to use for the next incremental crawl.<br /><br />`NULL` = None. |
44
+
|`stoplist_id`|**int**| ID of the [stoplist](../search/configure-and-manage-stopwords-and-stoplists-for-full-text-search.md) that is associated with this full-text index. |
45
+
|`data_space_id`|**int**| Filegroup where this full-text index resides. |
46
+
|`property_list_id`|**int**| ID of the search property list that is associated with this full-text index. `NULL` indicates that no search property list is associated with the full-text index. To obtain more information about this search property list, use the [sys.registered_search_property_lists](sys-registered-search-property-lists-transact-sql.md) catalog view. |
The following example uses a full-text index on the `HumanResources.JobCandidate` table of the [!INCLUDE [sssampledbobject-md](../../includes/sssampledbobject-md.md)] sample database. The example returns the object ID of the table, the search property list ID, and the stoplist ID of the stoplist used by the full-text index.
|**object_id**|**int**|ID of the object to which this full-text index belongs.|
31
-
|**unique_index_id**|**int**|ID of the corresponding unique, non-full-text index that is used to relate the full-text index to the rows.|
32
-
|**fulltext_catalog_id**|**int**|ID of the full-text catalog in which the full-text index resides.|
33
-
|**is_enabled**|**bit**|1 = Full-text index is currently enabled.|
34
-
|**change_tracking_state**|**char(1)**|State of change-tracking.<br /><br /> M = Manual<br /><br /> A = Auto<br /><br /> O = Off|
35
-
|**change_tracking_state_desc**|**nvarchar(60)**|Description of the state of change-tracking.<br /><br /> MANUAL<br /><br /> AUTO<br /><br /> OFF|
36
-
|**has_crawl_completed**|**bit**|Last crawl (population) that the full-text index has completed.|
37
-
|**crawl_type**|**char(1)**|Type of the current or last crawl.<br /><br /> F = Full crawl<br /><br /> I = Incremental, timestamp-based crawl<br /><br /> U = Update crawl, based on notifications<br /><br /> P = Full crawl is paused.|
38
-
|**crawl_type_desc**|**nvarchar(60)**|Description of the current or last crawl type.<br /><br /> FULL_CRAWL<br /><br /> INCREMENTAL_CRAWL<br /><br /> UPDATE_CRAWL<br /><br /> PAUSED_FULL_CRAWL|
39
-
|**crawl_start_date**|**datetime**|Start of the current or last crawl.<br /><br /> NULL = None.|
40
-
|**crawl_end_date**|**datetime**|End of the current or last crawl.<br /><br /> NULL = None.|
41
-
|**incremental_timestamp**|**binary(8)**|Timestamp value to use for the next incremental crawl.<br /><br /> NULL = None.|
42
-
|**stoplist_id**|**int**|ID of the [stoplist](../../relational-databases/search/configure-and-manage-stopwords-and-stoplists-for-full-text-search.md) that is associated with this full-text index.|
43
-
|**data_space_id**|**int**|Filegroup where this full-text index resides.|
44
-
|**property_list_id**|**int**|ID of the search property list that is associated with this full-text index. NULL indicates that no search property list is associated with the full-text index. To obtain more information about this search property list, use the [sys.registered_search_property_lists (Transact-SQL)](../../relational-databases/system-catalog-views/sys-registered-search-property-lists-transact-sql.md) catalog view.|
The following example uses a full-text index on the `HumanResources.JobCandidate` table of the [!INCLUDE [sssampledbobject-md](../../includes/sssampledbobject-md.md)] sample database. The example returns the object ID of the table, the search property list ID, and the stoplist ID of the stoplist used by the full-text index.
51
-
52
56
> [!NOTE]
53
-
> For the code example that creates this full-text index, see the "Examples" section of [CREATE FULLTEXT INDEX (Transact-SQL)](../../t-sql/statements/create-fulltext-index-transact-sql.md).
54
-
55
-
```
56
-
USE AdventureWorks2022;
57
-
GO
58
-
SELECT object_id, property_list_id, stoplist_id FROM sys.fulltext_indexes
59
-
where object_id = object_id('HumanResources.JobCandidate');
[Create and Manage Full-Text Indexes](../../relational-databases/search/create-and-manage-full-text-indexes.md)
70
-
[DROP FULLTEXT INDEX (Transact-SQL)](../../t-sql/statements/drop-fulltext-index-transact-sql.md)
71
-
[CREATE FULLTEXT INDEX (Transact-SQL)](../../t-sql/statements/create-fulltext-index-transact-sql.md)
72
-
[ALTER FULLTEXT INDEX (Transact-SQL)](../../t-sql/statements/alter-fulltext-index-transact-sql.md)
73
-
74
-
57
+
> For the code example that creates this full-text index, see the [Examples](../../t-sql/statements/create-fulltext-index-transact-sql.md#examples) section of [CREATE FULLTEXT INDEX](../../t-sql/statements/create-fulltext-index-transact-sql.md).
58
+
59
+
```sql
60
+
USE AdventureWorks2025;
61
+
GO
62
+
63
+
SELECT object_id,
64
+
property_list_id,
65
+
stoplist_id
66
+
FROMsys.fulltext_indexes
67
+
WHERE object_id = object_id('HumanResources.JobCandidate');
![learn-build-service-prod[bot]](https://avatars.githubusercontent.com/in/237442?v=4&size=40){kind=avatar}
0 commit comments