Merge pull request #35904 from MicrosoftDocs/main

Auto Publish – main to live - 2025-11-21 18:30 UTC

Author: learn-build-service-prod[bot]

.openpublishing.redirection.json

@@ -10663,7 +10663,7 @@
     {
       "source_path": "docs/sql-server/ai-artificial-intelligence-intelligent-applications.md",
       "redirect_url": "/sql/sql-server/artificial-intelligence-intelligent-applications",
-      "redirect_document_id": false  
+      "redirect_document_id": false
     },
     {
       "source_path": "docs/sql-server/sql-server-privacy-ver15.md",
@@ -48005,6 +48005,21 @@
       "redirect_url": "/previous-versions/sql/2014/tools/configuration-manager/sql-full-text-filter-daemon-launcher-sql-server-configuration-manager",
       "redirect_document_id": false
     },
+    {
+      "source_path": "docs/tools/configuration-manager/sql-full-text-filter-daemon-launcher-log-on-tab.md",
+      "redirect_url": "/sql/tools/configuration-manager/sql-full-text-filter-daemon-launcher-sql-server-configuration-manager",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/tools/configuration-manager/sql-full-text-filter-daemon-launcher-service-tab.md",
+      "redirect_url": "/sql/tools/configuration-manager/sql-full-text-filter-daemon-launcher-sql-server-configuration-manager",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/tools/configuration-manager/sql-full-text-filter-daemon-launcher-advanced.md",
+      "redirect_url": "/sql/tools/configuration-manager/sql-full-text-filter-daemon-launcher-sql-server-configuration-manager",
+      "redirect_document_id": false
+    },
     {
       "source_path": "docs/2014/tools/configuration-manager/sql-native-client-11-0-configuration.md",
       "redirect_url": "/previous-versions/sql/2014/tools/configuration-manager/sql-native-client-11-0-configuration",

docs/database-engine/install-windows/install-sql-server.md

@@ -59,7 +59,7 @@ Beginning with [!INCLUDE [sssql16-md](../../includes/sssql16-md.md)], [!INCLUDE
 The download location for [!INCLUDE [ssnoversion](../../includes/ssnoversion-md.md)] depends on the edition:
 
 - **[!INCLUDE [ssnoversion](../../includes/ssnoversion-md.md)] Enterprise, Standard, and Express editions** are licensed for production use. For the Enterprise and Standard Editions, contact your software vendor for the installation media. You can find purchasing information and a directory of Microsoft partners on the [Microsoft licensing page](https://www.microsoft.com/licensing/product-licensing/sql-server).
-- If you have a volume licensing agreement, for example an [Enterprise Agreement](https://www.microsoft.com/licensing/licensing-programs/enterprise), you can download software from the [Volume Licensing Service Center (VLSC)](https://www.microsoft.com/licensing/servicecenter/default.aspx).
+- If you have a volume licensing agreement, for example an [Enterprise Agreement](https://www.microsoft.com/licensing/licensing-programs/enterprise), you can download software from the [Microsoft 365 admin center](https://go.microsoft.com/fwlink/p/?linkid=2024339). The software's activation wizard automatically detects an embedded product key during installation.
 - [Free versions](https://www.microsoft.com/sql-server/sql-server-downloads).
 
 Other [!INCLUDE [ssnoversion](../../includes/ssnoversion-md.md)] components can be found here:

docs/relational-databases/system-stored-procedures/sp-refreshview-transact-sql.md

@@ -4,7 +4,7 @@ description: sp_refreshview updates the metadata for the specified non-schema-bo
 author: markingmyname
 ms.author: maghan
 ms.reviewer: randolphwest
-ms.date: 06/23/2025
+ms.date: 11/20/2025
 ms.service: sql
 ms.subservice: system-objects
 ms.topic: "reference"
@@ -46,20 +46,22 @@ The name of the view. *@viewname* is **nvarchar**, with no default. *@viewname*
 
 ## Remarks
 
-If a view isn't created with SCHEMABINDING, `sp_refreshview` should be run when changes are made to the objects underlying the view, which affect the definition of the view. Otherwise, the view might produce unexpected results when it's queried.
+If a view isn't created with `SCHEMABINDING`, `sp_refreshview` should be run when changes are made to the objects underlying the view, which affects the definition of the view. Otherwise, the view could produce unexpected results when you query it.
 
 ## Permissions
 
-Requires ALTER permission on the view and REFERENCES permission on common language runtime (CLR) user-defined types and XML schema collections that are referenced by the view columns.
+Requires `ALTER` permission on the view, and `REFERENCES` permission on common language runtime (CLR) user-defined types and XML schema collections that the view columns reference.
 
 ## Examples
 
+[!INCLUDE [article-uses-adventureworks](../../includes/article-uses-adventureworks.md)]
+
 ### A. Update the metadata of a view
 
 The following example refreshes the metadata for the view `Sales.vIndividualCustomer`.
 
 ```sql
-USE AdventureWorks2022;
+USE AdventureWorks2025;
 GO
 
 EXECUTE sp_refreshview N'Sales.vIndividualCustomer';
@@ -70,7 +72,7 @@ EXECUTE sp_refreshview N'Sales.vIndividualCustomer';
 Assume that the table `Person.Person` was changed in a way that would affect the definition of any views that are created on it. The following example creates a script that refreshes the metadata for all views that have a dependency on table `Person.Person`.
 
 ```sql
-USE AdventureWorks2022;
+USE AdventureWorks2025;
 GO
 
 SELECT DISTINCT 'EXECUTE sp_refreshview ''' + name + ''''
@@ -87,4 +89,3 @@ WHERE so.type = 'V'
 - [System stored procedures (Transact-SQL)](system-stored-procedures-transact-sql.md)
 - [sys.sql_expression_dependencies (Transact-SQL)](../system-catalog-views/sys-sql-expression-dependencies-transact-sql.md)
 - [sp_refreshsqlmodule (Transact-SQL)](sp-refreshsqlmodule-transact-sql.md)
-

docs/t-sql/includes/alter-workload-group.md

@@ -2,7 +2,7 @@
 author: rwestMSFT
 ms.author: randolphwest
 ms.reviewer: dfurman
-ms.date: 06/10/2025
+ms.date: 11/20/2025
 ms.service: sql
 ms.topic: include
 ms.custom:
@@ -98,7 +98,7 @@ Specifies the maximum number of simultaneous requests that are allowed to execut
 
 #### GROUP_MAX_TEMPDB_DATA_MB = *value*
 
-Specifies the maximum amount of space that a workload group can consume in the `tempdb` data files, in megabytes. *value* must be 0 or a positive number. Fractional values are allowed.
+Specifies the maximum amount of space that a workload group can consume in the `tempdb` data files, in megabytes. *value* must be 0, a positive number, or NULL. Fractional values are allowed.
 
 When the value is 0, `tempdb` space allocations by sessions in the workload group are not allowed. When a value isn't set, resource governor doesn't limit `tempdb` space consumption by the workload group.
 
@@ -108,7 +108,7 @@ When a request running in a workload group attempts to increase `tempdb` data sp
 
 #### GROUP_MAX_TEMPDB_DATA_PERCENT = *value*
 
-Specifies the maximum amount of space that a workload group can consume in the `tempdb` data files, in percent of the maximum `tempdb` size. For the definition of the maximum `tempdb` size, see [Percent limit configuration](../../relational-databases/resource-governor/tempdb-space-resource-governance.md#percent-limit-configuration). *value* must be in the range from 0 to 100. Fractional values are allowed.
+Specifies the maximum amount of space that a workload group can consume in the `tempdb` data files, in percent of the maximum `tempdb` size. For the definition of the maximum `tempdb` size, see [Percent limit configuration](../../relational-databases/resource-governor/tempdb-space-resource-governance.md#percent-limit-configuration). *value* must be in the range from 0 to 100, or NULL. Fractional values are allowed.
 
 When the value is 0, `tempdb` space allocations by sessions in the workload group are not allowed. When a value isn't set, resource governor doesn't limit `tempdb` space consumption by the workload group. When `GROUP_MAX_TEMPDB_DATA_MB` is set, or when `tempdb` maximum size isn't defined, `GROUP_MAX_TEMPDB_DATA_PERCENT` has no effect.
 

docs/t-sql/includes/create-workload-group.md

@@ -2,7 +2,7 @@
 author: rwestMSFT
 ms.author: randolphwest
 ms.reviewer: dfurman
-ms.date: 06/10/2025
+ms.date: 11/20/2025
 ms.service: sql
 ms.topic: include
 ms.custom:
@@ -102,7 +102,7 @@ Specifies the maximum number of simultaneous requests that are allowed to execut
 
 #### GROUP_MAX_TEMPDB_DATA_MB = *value*
 
-Specifies the maximum amount of space that a workload group can consume in the `tempdb` data files, in megabytes. *value* must be 0 or a positive number. Fractional values are allowed.
+Specifies the maximum amount of space that a workload group can consume in the `tempdb` data files, in megabytes. *value* must be 0, a positive number, or NULL. Fractional values are allowed.
 
 When the value is 0, `tempdb` space allocations by sessions in the workload group are not allowed. When a value isn't set, resource governor doesn't limit `tempdb` space consumption by the workload group.
 
@@ -112,7 +112,7 @@ When a request running in a workload group attempts to increase `tempdb` data sp
 
 #### GROUP_MAX_TEMPDB_DATA_PERCENT = *value*
 
-Specifies the maximum amount of space that a workload group can consume in the `tempdb` data files, in percent of the maximum `tempdb` size. For the definition of the maximum `tempdb` size, see [Percent limit configuration](../../relational-databases/resource-governor/tempdb-space-resource-governance.md#percent-limit-configuration). *value* must be in the range from 0 to 100. Fractional values are allowed.
+Specifies the maximum amount of space that a workload group can consume in the `tempdb` data files, in percent of the maximum `tempdb` size. For the definition of the maximum `tempdb` size, see [Percent limit configuration](../../relational-databases/resource-governor/tempdb-space-resource-governance.md#percent-limit-configuration). *value* must be in the range from 0 to 100, or NULL. Fractional values are allowed.
 
 When the value is 0, `tempdb` space allocations by sessions in the workload group are not allowed. When a value isn't set, resource governor doesn't limit `tempdb` space consumption by the workload group. When `GROUP_MAX_TEMPDB_DATA_MB` is set, or when `tempdb` maximum size isn't defined, `GROUP_MAX_TEMPDB_DATA_PERCENT` has no effect.