Merge pull request #35150 from rwestMSFT/rw-0827-expert

JillGrant615 · web-flow · commit ca4009c5d5d2 · 2025-08-27T20:11:08.000-06:00
Professional experts don't have to be certified
diff --git a/docs/database-engine/configure-windows/configure-the-cursor-threshold-server-configuration-option.md b/docs/database-engine/configure-windows/configure-the-cursor-threshold-server-configuration-option.md
@@ -24,7 +24,7 @@ The accuracy of the query optimizer to determine an estimate for the number of r
 
 ## Recommendations
 
-This option is an advanced option and should be changed only by an experienced database administrator or certified [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] professional.
+This option is an advanced option, and should be changed only by an experienced database professional.
 
 If you set `cursor threshold` to `-1`, all keysets are generated synchronously, which benefits small cursor sets. If you set `cursor threshold` to `0`, all cursor keysets are generated asynchronously. With other values, the query optimizer compares the number of expected rows in the cursor set and builds the keyset asynchronously if it exceeds the number set in `cursor threshold`. Don't set `cursor threshold` too low, because small result sets are better built synchronously.
 
diff --git a/docs/database-engine/configure-windows/configure-the-default-full-text-language-server-configuration-option.md b/docs/database-engine/configure-windows/configure-the-default-full-text-language-server-configuration-option.md
@@ -23,7 +23,7 @@ The value of the `default full-text language` option is used in a full-text inde
 
 ## Recommendations
 
-This option is an advanced option and should be changed only by an experienced database administrator or certified [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] professional.
+This option is an advanced option, and should be changed only by an experienced database professional.
 
 The `default full-text language` option requires a locale identifier (LCID) value. For a list of supported LCIDs and their related languages, see [sys.fulltext_languages](../../relational-databases/system-catalog-views/sys-fulltext-languages-transact-sql.md). Other languages might also be available from independent software vendors, for example. If no specific language is found, the Full-Text Engine automatically switches to the primary language.
 
diff --git a/docs/database-engine/configure-windows/configure-the-fill-factor-server-configuration-option.md b/docs/database-engine/configure-windows/configure-the-fill-factor-server-configuration-option.md
@@ -18,7 +18,7 @@ This article describes how to configure the `fill factor` server configuration o
 
 ## Recommendations
 
-This option is an advanced option and should be changed only by an experienced database administrator or certified [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] professional.
+This option is an advanced option, and should be changed only by an experienced database professional.
 
 ## Permissions
 
diff --git a/docs/database-engine/configure-windows/configure-the-index-create-memory-server-configuration-option.md b/docs/database-engine/configure-windows/configure-the-index-create-memory-server-configuration-option.md
@@ -26,7 +26,7 @@ The run value for this option doesn't exceed the actual amount of memory that ca
 
 ## Recommendations
 
-This option is an advanced option and should be changed only by an experienced database administrator or certified [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] professional.
+This option is an advanced option, and should be changed only by an experienced database professional.
 
 The `index create memory` option is self-configuring and usually works without requiring adjustment. However, if you experience difficulties creating indexes, consider increasing the value of this option from its run value.
 
diff --git a/docs/database-engine/configure-windows/configure-the-locks-server-configuration-option.md b/docs/database-engine/configure-windows/configure-the-locks-server-configuration-option.md
@@ -21,7 +21,7 @@ This article describes how to configure the `locks` server configuration option
 
 ## Recommendations
 
-This option is an advanced option and should be changed only by an experienced database administrator or certified [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] professional.
+This option is an advanced option, and should be changed only by an experienced database professional.
 
 When the server is started with `locks` set to `0`, the lock manager acquires sufficient memory from the [!INCLUDE [ssDE](../../includes/ssde-md.md)] for an initial pool of 2,500 lock structures. As the lock pool is exhausted, more memory is acquired for the pool.
 
diff --git a/docs/database-engine/configure-windows/configure-the-max-degree-of-parallelism-server-configuration-option.md b/docs/database-engine/configure-windows/configure-the-max-degree-of-parallelism-server-configuration-option.md
@@ -30,7 +30,7 @@ For more on `MAXDOP` in [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.m
 
 ## Considerations
 
-This option is an advanced option and should be changed only by an experienced database administrator or certified [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] professional.
+This option is an advanced option, and should be changed only by an experienced database professional.
 
 If the affinity mask option isn't set to the default, it might restrict the number of processors available to [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] on symmetric multiprocessing (SMP) systems.
 
diff --git a/docs/database-engine/configure-windows/configure-the-max-worker-threads-server-configuration-option.md b/docs/database-engine/configure-windows/configure-the-max-worker-threads-server-configuration-option.md
@@ -56,7 +56,9 @@ The `max worker threads` server configuration option doesn't limit all threads t
 
 ## Recommendations
 
-This option is an advanced option and should be changed only by an experienced database administrator or certified [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] professional. If you suspect that there's a performance problem, it's probably not the availability of worker threads. The cause is more likely related to activities that occupy the worker threads and don't release them. Examples include long-running queries or bottlenecks on the system (I/O, blocking, latch waits, network waits) that cause long-waiting queries. It's best to find the root cause of a performance issue before you change the max worker threads setting. For more information on assessing performance, see [Monitor and Tune for Performance](../../relational-databases/performance/monitor-and-tune-for-performance.md).
+This option is an advanced option, and should be changed only by an experienced database professional.
+
+If you suspect that there's a performance problem, it's probably not the availability of worker threads. The cause is more likely related to activities that occupy the worker threads and don't release them. Examples include long-running queries or bottlenecks on the system (I/O, blocking, latch waits, network waits) that cause long-waiting queries. It's best to find the root cause of a performance issue before you change the max worker threads setting. For more information on assessing performance, see [Monitor and Tune for Performance](../../relational-databases/performance/monitor-and-tune-for-performance.md).
 
 Thread pooling helps optimize performance when a large number of clients connect to the server. Usually, a separate operating system thread is created for each query request. However, with hundreds of connections to the server, using one thread per query request can consume large amounts of system resources. The `max worker threads` option enables [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] to create a pool of worker threads to service a larger number of query requests, which improves performance.
 
diff --git a/docs/database-engine/configure-windows/configure-the-media-retention-server-configuration-option.md b/docs/database-engine/configure-windows/configure-the-media-retention-server-configuration-option.md
@@ -24,7 +24,7 @@ If you use the backup medium before the set number of days has passed, [!INCLUDE
 
 ## Recommendations
 
-This option is an advanced option and should be changed only by an experienced database administrator or certified [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] professional.
+This option is an advanced option, and should be changed only by an experienced database professional.
 
 The `media retention` option can be overridden by using the `RETAINDAYS` clause of the [BACKUP](../../t-sql/statements/backup-transact-sql.md) statement.
 
diff --git a/docs/database-engine/configure-windows/configure-the-min-memory-per-query-server-configuration-option.md b/docs/database-engine/configure-windows/configure-the-min-memory-per-query-server-configuration-option.md
@@ -28,7 +28,7 @@ The amount of min memory per query has precedence over the [index create memory]
 
 ## Recommendations
 
-This option is an advanced option and should be changed only by an experienced database administrator or certified [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] professional.
+This option is an advanced option, and should be changed only by an experienced database professional.
 
 The [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] query processor tries to determine the optimal amount of memory to allocate to a query. The min memory per query option lets the administrator specify the minimum amount of memory any single query receives. Queries generally receive more memory than this, if they have hash and sort operations on a large volume of data. Increasing the value of min memory per query might improve performance for some small to medium-sized queries, but doing so could lead to increased competition for memory resources. The min memory per query option includes memory allocated for sort operations.
 
diff --git a/docs/database-engine/configure-windows/configure-the-network-packet-size-server-configuration-option.md b/docs/database-engine/configure-windows/configure-the-network-packet-size-server-configuration-option.md
@@ -33,7 +33,7 @@ The maximum network packet size for encrypted connections is 16,383 bytes.
 
 ## Recommendations
 
-This option is an advanced option and should be changed only by an experienced database administrator or certified [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] professional.
+This option is an advanced option, and should be changed only by an experienced database professional.
 
 If an application does bulk copy operations or sends or receives large amounts of text or image data, a packet size larger than the default might improve efficiency because it results in fewer network read-and-write operations. If an application sends and receives small amounts of information, the packet size can be set to 512 bytes, which is sufficient for most data transfers.
 
diff --git a/docs/database-engine/configure-windows/configure-the-query-governor-cost-limit-server-configuration-option.md b/docs/database-engine/configure-windows/configure-the-query-governor-cost-limit-server-configuration-option.md
@@ -20,7 +20,7 @@ This article describes how to configure the `query governor cost limit` server c
 
 ## Recommendations
 
-This option is an advanced option and should be changed only by an experienced database administrator or certified [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] professional.
+This option is an advanced option, and should be changed only by an experienced database professional.
 
 To change the value query governor cost limit on a per-connection basis, use the [SET QUERY_GOVERNOR_COST_LIMIT](../../t-sql/statements/set-query-governor-cost-limit-transact-sql.md) statement.
 
diff --git a/docs/database-engine/configure-windows/configure-the-query-wait-server-configuration-option.md b/docs/database-engine/configure-windows/configure-the-query-wait-server-configuration-option.md
@@ -23,7 +23,7 @@ This article describes how to configure the **query wait** server configuration
 
 ## Recommendations
 
-This option is an advanced option and should be changed only by an experienced database administrator or certified [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] professional.
+This option is an advanced option, and should be changed only by an experienced database professional.
 
 ## Permissions
 
diff --git a/docs/database-engine/configure-windows/configure-the-recovery-interval-server-configuration-option.md b/docs/database-engine/configure-windows/configure-the-recovery-interval-server-configuration-option.md
@@ -33,7 +33,7 @@ The recovery interval affects only databases that use the default target recover
 
 ## Recommendations
 
-This option is an advanced option and should be changed only by an experienced database administrator or certified [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] professional.
+This option is an advanced option, and should be changed only by an experienced database professional.
 
 Typically, we recommend that you keep the recovery interval at `0`, unless you experience performance problems. If you decide to increase the recovery-interval setting, we recommend increasing it gradually by small increments and evaluating the effect of each incremental increase on recovery performance.
 
diff --git a/docs/database-engine/configure-windows/configure-the-scan-for-startup-procs-server-configuration-option.md b/docs/database-engine/configure-windows/configure-the-scan-for-startup-procs-server-configuration-option.md
@@ -18,7 +18,7 @@ This article describes how to configure the `scan for startup procs` server conf
 
 ## Recommendations
 
-This option is an advanced option and should be changed only by an experienced database administrator or certified [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] professional.
+This option is an advanced option, and should be changed only by an experienced database professional.
 
 The value for this option can be set by using `sp_configure`; however, the option is set automatically if you use `sp_procoption`, which is used to mark or unmark automatically run stored procedures. When `sp_procoption` is used to mark the first stored procedure as an autoproc, this option is set automatically to a value of `1`. When `sp_procoption` is used to unmark the last stored procedure as an autoproc, this option is automatically set to a value of `0`. If you use `sp_procoption` to mark and unmark autoprocs, and if you always unmark autoprocs before dropping them, there's no need to set this option manually.
 
diff --git a/docs/database-engine/configure-windows/configure-the-two-digit-year-cutoff-server-configuration-option.md b/docs/database-engine/configure-windows/configure-the-two-digit-year-cutoff-server-configuration-option.md
@@ -19,7 +19,7 @@ This article describes how to configure the `two digit year cutoff` server confi
 
 ## Recommendations
 
-This option is an advanced option and should be changed only by an experienced database administrator or certified [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] professional.
+This option is an advanced option, and should be changed only by an experienced database professional.
 
 OLE Automation objects use 2030 as the two-digit cutoff year. You can use the `two digit year cutoff` option to provide consistency in date values between [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] and client applications.
 
diff --git a/docs/database-engine/configure-windows/configure-the-user-connections-server-configuration-option.md b/docs/database-engine/configure-windows/configure-the-user-connections-server-configuration-option.md
@@ -26,7 +26,7 @@ To determine the maximum number of user connections that your system allows, you
 
 ## Recommendations
 
-This option is an advanced option, and should be changed only by an experienced database administrator or certified [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] professional.
+This option is an advanced option, and should be changed only by an experienced database professional.
 
 Using the `user connections` option helps avoid overloading the server with too many concurrent connections. You can estimate the number of connections based on system and user requirements. For example, on a system with many users, each user wouldn't usually require a unique connection. Connections can be shared among users. Users running OLE DB applications need a connection for each open connection object, users running Open Database Connectivity (ODBC) applications need a connection for each active connection handle in the application, and users running DB-Library applications need one connection for each process started that calls the DB-Library `dbopen` function.
 
diff --git a/docs/database-engine/configure-windows/disallow-results-from-triggers-server-configuration-option.md b/docs/database-engine/configure-windows/disallow-results-from-triggers-server-configuration-option.md
@@ -41,7 +41,7 @@ SELECT [name], value_in_use
 FROM sys.configurations
 WHERE [name] LIKE 'disallow results from triggers';
 
--- Set the disallow results from triggers option to 1. This is an advanced option so that must be enabled first
+-- Set the disallow results from triggers option to 1. This option is an advanced option so that must be enabled first
 EXECUTE sp_configure 'show advanced options', 1;
 
 RECONFIGURE;
diff --git a/docs/database-engine/configure-windows/server-configuration-options-sql-server.md b/docs/database-engine/configure-windows/server-configuration-options-sql-server.md
@@ -38,7 +38,7 @@ ms.custom:
 You can manage and optimize [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] and [!INCLUDE [ssazuremi-md](../../includes/ssazuremi-md.md)] resources through configuration options by using [!INCLUDE [ssManStudioFull](../../includes/ssmanstudiofull-md.md)] or the `sp_configure` system stored procedure. The most commonly used server configuration options are available through [!INCLUDE [ssManStudioFull](../../includes/ssmanstudiofull-md.md)]; all configuration options are accessible through `sp_configure`. Consider the effects on your system carefully before setting these options. For more information, see [View or change server properties (SQL Server)](view-or-change-server-properties-sql-server.md).
 
 > [!IMPORTANT]
-> Advanced options should be changed only by an experienced database administrator.
+> Advanced options should be changed only by an experienced database professional.
 
 ## Categories of configuration options
 
@@ -81,7 +81,7 @@ For a configuration option that isn't dynamic there's no way to tell if the `REC
 
 The following table lists all available configuration options, the range of possible settings, the default values, and the supported product ([!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] or [!INCLUDE [ssazuremi-md](../../includes/ssazuremi-md.md)]). Configuration options are marked with letter codes as follows:
 
-- **A** = Advanced options, which should be changed only by an experienced database administrator or a certified SQL Server professional, and which require setting `show advanced options` to `1`.
+- **A** = Advanced options, which should be changed only by an experienced database professional, and which require setting `show advanced options` to `1`.
 
 - **RR** = Options requiring a restart of the [!INCLUDE [ssDE](../../includes/ssde-md.md)].
 
diff --git a/docs/relational-databases/query-processing-architecture-guide.md b/docs/relational-databases/query-processing-architecture-guide.md
@@ -1011,7 +1011,7 @@ When [!INCLUDE [ssNoVersion](../includes/ssnoversion-md.md)] parameterizes liter
 
 Consider the following when you set the `PARAMETERIZATION` option to FORCED:
 
-- Forced parameterization, in effect, changes the literal constants in a query to parameters when compiling a query. Therefore, the Query Optimizer can choose suboptimal plans for queries. In particular, the Query Optimizer is less likely to match the query to an indexed view or an index on a computed column. It might also choose suboptimal plans for queries posed on partitioned tables and distributed partitioned views. Forced parameterization shouldn't be used for environments that rely heavily on indexed views and indexes on computed columns. Generally, the `PARAMETERIZATION FORCED` option should only be used by experienced database administrators after determining that doing this doesn't adversely affect performance.
+- Forced parameterization, in effect, changes the literal constants in a query to parameters when compiling a query. Therefore, the Query Optimizer can choose suboptimal plans for queries. In particular, the Query Optimizer is less likely to match the query to an indexed view or an index on a computed column. It might also choose suboptimal plans for queries posed on partitioned tables and distributed partitioned views. Forced parameterization shouldn't be used for environments that rely heavily on indexed views and indexes on computed columns. Generally, the `PARAMETERIZATION FORCED` option should only be used by experienced database professionals after determining that doing this doesn't adversely affect performance.
 - Distributed queries that reference more than one database are eligible for forced parameterization as long as the `PARAMETERIZATION` option is set to `FORCED` in the database whose context the query is running.
 - Setting the `PARAMETERIZATION` option to `FORCED` flushes all query plans from the plan cache of a database, except those that currently are compiling, recompiling, or running. Plans for queries that are compiling or running during the setting change are parameterized the next time the query is executed.
 - Setting the `PARAMETERIZATION` option is an online operation that it requires no database-level exclusive locks.
diff --git a/docs/relational-databases/sql-server-index-design-guide.md b/docs/relational-databases/sql-server-index-design-guide.md
@@ -95,7 +95,7 @@ The following tasks make up our recommended strategy for designing indexes:
 
 ## General index design guidelines
 
-Experienced database administrators can design a good set of indexes, but this task is complex, time-consuming, and error-prone even for moderately complex databases and workloads. Understanding the characteristics of your database, queries, and data columns can help you design optimal indexes.
+Experienced database professionals can design a good set of indexes, but this task is complex, time-consuming, and error-prone even for moderately complex databases and workloads. Understanding the characteristics of your database, queries, and data columns can help you design optimal indexes.
 
 ### Database considerations
 
diff --git a/docs/relational-databases/thread-and-task-architecture-guide.md b/docs/relational-databases/thread-and-task-architecture-guide.md
