[SCOPED] Reformat "Trace Flag" to sentence case

Author: rwestMSFT

azure-sql/managed-instance/transact-sql-tsql-differences-sql-server.md

@@ -344,7 +344,7 @@ A SQL Managed Instance can't access file shares and Windows folders, so the foll
 
 Undocumented DBCC statements that are enabled in SQL Server aren't supported in SQL Managed Instance.
 
-- Only a limited number of Global Trace flags are supported. Session-level `Trace flags` aren't supported. See [Trace Flags](/sql/t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql).
+- Only a limited number of Global Trace flags are supported. Session-level `Trace flags` aren't supported. See [Set trace flags with DBCC TRACEON](/sql/t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql).
 - [DBCC TRACEOFF](/sql/t-sql/database-console-commands/dbcc-traceoff-transact-sql) and [DBCC TRACEON](/sql/t-sql/database-console-commands/dbcc-traceon-transact-sql) work with the limited number of global trace-flags.
 - [DBCC CHECKDB](/sql/t-sql/database-console-commands/dbcc-checkdb-transact-sql) with options REPAIR_ALLOW_DATA_LOSS, REPAIR_FAST, and REPAIR_REBUILD can't be used because database can't be set in `SINGLE_USER` mode - see [ALTER DATABASE differences](#alter-database-statement). Potential database corruption is handled by the Azure support team. Contact Azure support if there's any indication of database corruption.
 

data-migration/sql-server/managed-instance/assessment-rules.md

@@ -503,7 +503,7 @@ Azure SQL Managed Instance supports only limited number of global trace flags. S
 **Recommendation**  
 Review affected objects section in Azure Migrate to see all trace flags that aren't supported in Azure SQL Managed Instance and evaluate if they can be removed. Alternatively, migrate to SQL Server on Azure VMs.
 
-More information: [Trace flags](/sql/t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql#trace-flags)
+For more information, see [Set trace flags with DBCC TRACEON](/sql/t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql).
 
 ## <a id="WindowsAuthentication"></a> Windows authentication
 

docs/database-engine/availability-groups/windows/failover-and-failover-modes-always-on-availability-groups.md

@@ -78,7 +78,7 @@ In certain situations, with a DR failover, as the secondary replica transitions
 To improve undo-of-redo for this scenario, [!INCLUDE [sssql25-md](../../../includes/sssql25-md.md)] introduces an update to the synchronization mechanism so that the availability group now performs page requests asynchronously, and in batches.
 
 Consider the following: 
-- The improvement to the synchronization mechanism is enabled by default. To disable the improvement and revert to default behavior, enable [Trace Flag 12348](../../../t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql.md#tf12348) on all replicas in an availability group that are currently secondaries, or that might be secondaries in the future. 
+- The improvement to the synchronization mechanism is enabled by default. To disable the improvement and revert to default behavior, enable [trace flag 12348](../../../t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql.md#tf12348) on all replicas in an availability group that are currently secondaries, or that might be secondaries in the future. 
 - If the AG replicas don't have network latency, this improvement might not improve undo-of-redo.
 
 ### Databases switch to resolving state after a failure

docs/database-engine/availability-groups/windows/monitor-performance-for-always-on-availability-groups.md

@@ -40,13 +40,13 @@ After the logs have been captured on the primary replica, they are subject to tw
 
 In addition to the flow control gates, there's another factor that can prevent the log messages from being sent. The synchronization of replicas ensures that the messages are sent and applied in the order of the log sequence numbers (LSN). Before a log message is sent, its LSN also checked against the lowest acknowledged LSN number to make sure that it's less than one of thresholds (depending on the message type). If the gap between the two LSN numbers is larger than the threshold, the messages aren't sent. Once the gap is below the threshold again, the messages are sent.
 
-[!INCLUDE [sssql22-md](../../../includes/sssql22-md.md)] increases the limits to the number of messages that each gate allows. By using Trace Flag 12310, the increased limit is also available to the following versions of SQL Server: [!INCLUDE [sssql19-md](../../../includes/sssql19-md.md)] CU9, [!INCLUDE [sssql17-md](../../../includes/sssql17-md.md)] CU18, [!INCLUDE [sssql16-md](../../../includes/sssql16-md.md)] SP1 CU16.
+[!INCLUDE [sssql22-md](../../../includes/sssql22-md.md)] increases the limits to the number of messages that each gate allows. By using trace flag 12310, the increased limit is also available to the following versions of SQL Server: [!INCLUDE [sssql19-md](../../../includes/sssql19-md.md)] CU9, [!INCLUDE [sssql17-md](../../../includes/sssql17-md.md)] CU18, [!INCLUDE [sssql16-md](../../../includes/sssql16-md.md)] SP1 CU16.
 
 The following table compares message limits:
 
 # [New limits](#tab/new-limits)
 
-For versions of SQL Server that enable Trace Flag 12310, namely [!INCLUDE [sssql22-md](../../../includes/sssql22-md.md)], [!INCLUDE [sssql19-md](../../../includes/sssql19-md.md)] CU9, [!INCLUDE [sssql17-md](../../../includes/sssql17-md.md)] CU18, [!INCLUDE [sssql16-md](../../../includes/sssql16-md.md)] SP1 CU16, and later versions, see the following limits:
+For versions of SQL Server that enable trace flag 12310, namely [!INCLUDE [sssql22-md](../../../includes/sssql22-md.md)], [!INCLUDE [sssql19-md](../../../includes/sssql19-md.md)] CU9, [!INCLUDE [sssql17-md](../../../includes/sssql17-md.md)] CU18, [!INCLUDE [sssql16-md](../../../includes/sssql16-md.md)] SP1 CU16, and later versions, see the following limits:
 
 | Level | Number of gates | Number of messages | Useful metrics |
 | --- | --- | --- | --- |
@@ -55,7 +55,7 @@ For versions of SQL Server that enable Trace Flag 12310, namely [!INCLUDE [sssql
 
 # [Old limits](#tab/old-limits)
 
-For unsupported SQL Server versions, or supported SQL Server versions (starting with SQL Server 2019 CU9, SQL Server 2017 CU18, and SQL Server 2016 SP1 CU16) that **do not** have Trace Flag 12310 enabled, see the following limits:
+For unsupported SQL Server versions, or supported SQL Server versions (starting with SQL Server 2019 CU9, SQL Server 2017 CU18, and SQL Server 2016 SP1 CU16) that **do not** have trace flag 12310 enabled, see the following limits:
 
 | Level | Number of gates | Number of messages | Useful metrics |
 | --- | --- | --- | --- |

docs/database-engine/availability-groups/windows/replicate-track-change-data-capture-always-on-availability.md

@@ -60,9 +60,9 @@ The log reader agent has the following changes.
 
   When the publisher has only two availability replicas (one primary and one secondary) and a failover happens, the original primary replica remains down because the log reader doesn't move forward until all secondary databases are brought back online or until the failing secondary replicas are removed from the availability group. The log reader, now running against the secondary database, doesn't proceed forward since the AG can't harden any changes to any secondary database. To allow the log reader to proceed further and still have disaster recovery capacity, remove the original primary replica from the availability group using ALTER AVAILABITY GROUP <group_name> REMOVE REPLICA. Then add a new secondary replica to the availability group.
 
-- **Trace Flag 1448**
+- **Trace flag 1448**
 
-  Trace Flag 1448 enables the replication log reader to move forward even if the asynchronous secondary replicas haven't acknowledged the reception of a change. Even with this trace flag enabled, the log reader always waits for the synchronous secondary replicas (They could become asynchronous commit mode as documented [here](availability-modes-always-on-availability-groups.md), so log reader can move forward). The log reader doesn't go beyond the min ack of the synchronous secondary replicas. This trace flag applies to the instance of [!INCLUDE [ssNoVersion](../../../includes/ssnoversion-md.md)], not just to an availability group, an availability database, or a log reader instance. This trace flag must be enabled on the publisher instance. It takes effect immediately without a restart. It can be activated ahead of time or when an asynchronous secondary replica fails.
+  Trace flag 1448 enables the replication log reader to move forward even if the asynchronous secondary replicas haven't acknowledged the reception of a change. Even with this trace flag enabled, the log reader always waits for the synchronous secondary replicas (They could become asynchronous commit mode as documented [here](availability-modes-always-on-availability-groups.md), so log reader can move forward). The log reader doesn't go beyond the min ack of the synchronous secondary replicas. This trace flag applies to the instance of [!INCLUDE [ssNoVersion](../../../includes/ssnoversion-md.md)], not just to an availability group, an availability database, or a log reader instance. This trace flag must be enabled on the publisher instance. It takes effect immediately without a restart. It can be activated ahead of time or when an asynchronous secondary replica fails.
 
 <a id="StoredProcs"></a>
 

docs/database-engine/configure-windows/configure-the-max-degree-of-parallelism-server-configuration-option.md

@@ -48,7 +48,7 @@ You can override the max degree of parallelism server configuration value:
 
 Index operations that create or rebuild an index, or that drop a clustered index, can be resource intensive. You can override the max degree of parallelism value for index operations by specifying the `MAXDOP` index option in the index statement. The `MAXDOP` value is applied to the statement at execution time and isn't stored in the index metadata. For more information, see [Configure Parallel Index Operations](../../relational-databases/indexes/configure-parallel-index-operations.md).
 
-In addition to queries and index operations, this option also controls the parallelism of `DBCC CHECKTABLE`, `DBCC CHECKDB`, and `DBCC CHECKFILEGROUP`. You can disable parallel execution plans for these statements by using Trace Flag 2528. For more information, see [Trace Flag 2528](../../t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql.md#tf2528).
+In addition to queries and index operations, this option also controls the parallelism of `DBCC CHECKTABLE`, `DBCC CHECKDB`, and `DBCC CHECKFILEGROUP`. You can disable parallel execution plans for these statements by using trace flag 2528. For more information, see [trace flag 2528](../../t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql.md#tf2528).
 
 [!INCLUDE [sssql22-md](../../includes/sssql22-md.md)] introduced Degree of Parallelism (DOP) Feedback, a new feature to improve query performance by identifying parallelism inefficiencies for repeating queries, based on elapsed time and waits. DOP feedback is part of the [intelligent query processing](../../relational-databases/performance/intelligent-query-processing.md) family of features, and addresses suboptimal usage of parallelism for repeating queries. For information about DOP feedback, visit [Degree of parallelism (DOP) feedback](../../relational-databases/performance/intelligent-query-processing-degree-parallelism-feedback.md).
 
@@ -145,7 +145,7 @@ The setting takes effect immediately without restarting the server.
 
 - [Intelligent query processing in SQL databases](../../relational-databases/performance/intelligent-query-processing.md)
 - [Query processing architecture guide](../../relational-databases/query-processing-architecture-guide.md)
-- [DBCC TRACEON - Trace Flags (Transact-SQL)](../../t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql.md)
+- [Set trace flags with DBCC TRACEON (Transact-SQL)](../../t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql.md)
 - [Query Store hints](../../relational-databases/performance/query-store-hints.md)
 - [Query hints (Transact-SQL)](../../t-sql/queries/hints-transact-sql-query.md)
 - [USE HINT query hint](../../t-sql/queries/hints-transact-sql-query.md#use_hint)

docs/database-engine/configure-windows/database-engine-service-startup-options.md

@@ -63,7 +63,7 @@ The following screenshot shows the Startup Parameters tab in the SQL Server Prop
 | `-mClient Application Name` | Limits the connections to those using a specific application name in the client connection string. For example, `-mSQLCMD` limits connections to a single connection from the **sqlcmd** utility. Use this option when you're starting [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] in single-user mode and an unknown client application is taking the only available connection. Use `"Microsoft SQL Server Management Studio - Query"` to connect with the SQL Server Management Studio (SSMS) Query Editor. The SSMS Query Editor option can't be configured by using [!INCLUDE [ssNoVersion_md](../../includes/ssnoversion-md.md)] Configuration Manager because it includes the dash (`-`) character.<br /><br />Client Application Name is case sensitive. Double quotes are required when [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] is started from the command line if the application name contains spaces or special characters. Don't use double quotes in [!INCLUDE [ssNoVersion_md](../../includes/ssnoversion-md.md)] Configuration Manager.<br /><br />For more information about setting startup options in SQL Server Configuration Manager, see [Use SQL Server Configuration Manager](scm-services-configure-server-startup-options.md#SSMSProcedure).<br /><br />**Examples when starting from the command line:**<br /><br />`C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\Binn\sqlservr -s MSSQLSERVER -m"Microsoft SQL Server Management Studio - Query"`<br /><br />`C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\Binn\sqlservr -s MSSQLSERVER -mSQLCMD`<br /><br />**Security note:** Don't use this option as a security feature. The client application provides the client application name, and can provide a false name as part of the connection string. |
 | `-n` | Doesn't use the Windows application log to record [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] events. If you start an instance of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] with `-n`, we recommend that you also use the `-e` startup option. Otherwise, [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] events aren't logged. |
 | `-s` | Allows you to start a named instance of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)]. Without the `-s` parameter set, the default instance tries to start. You must switch to the appropriate `BINN` directory for the instance at a command prompt before starting `sqlservr.exe`. For example, if Instance1 were to use `\mssql$Instance1` for its binaries, the user must be in the `\mssql$Instance1\binn` directory to start `sqlservr.exe -s instance1`. |
-| `-T <trace-number>` | Indicates that an instance of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] should be started with a specified trace flag (`<trace-number>`) in effect. Trace flags are used to start the server with nonstandard behavior. For more information, see [DBCC TRACEON - Trace Flags](../../t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql.md).<br /><br />**Important:** When specifying a trace flag with the `-T` option, use an uppercase `T` to pass the trace flag number and no space between the `-T` option and the number of the trace flag. A lowercase `t` is accepted by [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)], but this sets other internal trace flags that are required only by [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] support engineers. (Parameters specified in the Control Panel startup window aren't read.) |
+| `-T <trace-number>` | Indicates that an instance of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] should be started with a specified trace flag (`<trace-number>`) in effect. Trace flags are used to start the server with nonstandard behavior. For more information, see [Set trace flags with DBCC TRACEON](../../t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql.md).<br /><br />**Important:** When specifying a trace flag with the `-T` option, use an uppercase `T` to pass the trace flag number and no space between the `-T` option and the number of the trace flag. A lowercase `t` is accepted by [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)], but this sets other internal trace flags that are required only by [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] support engineers. (Parameters specified in the Control Panel startup window aren't read.) |
 | `-x` | Disables the following monitoring features:<br /><br />- [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] performance monitor counters<br />- Keeping CPU time and cache-hit ratio statistics<br />- Collecting information for the `DBCC SQLPERF` command<br />- Collecting information for some dynamic management views<br />- Many extended-events event points<br /><br />**Warning:** When you use the `-x` startup option, the information that is available for you to diagnose performance and functional problems with [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] is greatly reduced. |
 | `-E` | Increases the number of extents that are allocated for each file in a filegroup. This option might be helpful for data warehouse applications that have a limited number of users running index or data scans. It shouldn't be used in other applications because it might adversely affect performance. This option isn't supported in 32-bit releases of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)]. |
 

docs/database-engine/configure-windows/diagnostic-connection-for-database-administrators.md

@@ -69,7 +69,7 @@ Because the DAC exists solely for diagnosing server problems in rare circumstanc
 
 - To guarantee that there are resources available for the connection, only one DAC is allowed per instance of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)]. If a DAC connection is already active, any new request to connect through the DAC is denied with error 17810.
 
-- To conserve resources, [!INCLUDE [ssExpress](../../includes/ssexpress-md.md)] doesn't listen on the DAC port unless started with Trace Flag 7806.
+- To conserve resources, [!INCLUDE [ssExpress](../../includes/ssexpress-md.md)] doesn't listen on the DAC port unless started with trace flag 7806.
 
 - The DAC initially attempts to connect to the default database associated with the login. After it's successfully connected, you can connect to the `master` database. If the default database is offline or otherwise not available, the connection will return error 4060. However, it will succeed if you override the default database to connect to the `master` database instead using the following command:
 
@@ -142,4 +142,4 @@ sqlcmd -S serverName.database.windows.net,1434 -U sa -P <StrongPassword> -d Adve
 - [DBCC INPUTBUFFER (Transact-SQL)](../../t-sql/database-console-commands/dbcc-inputbuffer-transact-sql.md)
 - [Server configuration options](server-configuration-options-sql-server.md)
 - [Transaction Related Dynamic Management Views and Functions (Transact-SQL)](../../relational-databases/system-dynamic-management-views/transaction-related-dynamic-management-views-and-functions-transact-sql.md)
-- [Trace Flags (Transact-SQL)](../../t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql.md)
+- [Set trace flags with DBCC TRACEON (Transact-SQL)](../../t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql.md)