Merge pull request #24060 from MicrosoftDocs/FromPublicRepo

Confirm merge from FromPublicRepo to main to sync with https://github.com/MicrosoftDocs/sql-docs (branch live)

Author: huypub

docs/t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql.md

@@ -157,8 +157,9 @@ The following table lists and describes the trace flags that are available in [!
 |<a name="tf4616"></a>**4616**|Makes server-level metadata visible to application roles. In [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], an application role cannot access metadata outside its own database because application roles are not associated with a server-level principal. This is a change of behavior from earlier versions of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. Setting this global flag disables the new restrictions, and allows for application roles to access server-level metadata.<br /><br />**Scope**: global only|
 |<a name="tf4618"></a>**4618**|Limits the number of entries in the TokenAndPermUserStore cache store to 1,024. When used together with trace flag 4610 increases the number of entries in the TokenAndPermUserStore cache store to 8,192. For more information on troubleshooting TokenAndPermUserStore cache size issues, see this [Microsoft Support article](https://support.microsoft.com/topic/queries-take-a-longer-time-to-finish-running-when-the-size-of-the-tokenandpermuserstore-cache-grows-in-sql-server-2005-ad1622e7-3bb5-7902-19a0-5d0e6271033d).<br /><br />**Scope:** global only|
 |<a name="tf4621"></a>**4621**|Limits the number of entries in the TokenAndPermUserStore cache store to the number specified by the user in a registry key. For more information, see this [Microsoft Support article](https://support.microsoft.com/kb/959823).<br /><br />**Scope:** global only|
+|<a name="tf4631"></a>**4631**|Disables SHA2_256/AES256 for hashing passwords that generate encryption keys. For more information, see this [Microsoft Support article](https://support.microsoft.com/kb/4053407).<br /><br />**Note:** This trace flag applies to [!INCLUDE[ssSQL17](../../includes/sssql17-md.md)], and higher builds.<br /><br />**Scope:** global only|
 |<a name="tf5004"></a>**5004**|Pauses TDE encryption scan and causes encryption scan worker to exit without doing any work. The database will continue to be in encrypting state (encryption in progress). To resume re-encryption scan, disable trace flag 5004 and run ALTER DATABASE <database_name> SET ENCRYPTION ON. <br /><br />**Scope:** global only|
-|<a name="tf6408"></a>**6408**|Enables visibility of the estimated execution plan to see the remote query plan of PolyBase pushdown computation. **Note:** Starting with [!INCLUDE[sssql19](../../includes/sssql19-md.md)]. For more information, see [How to tell if external pushdown occurred](../../relational-databases/polybase/polybase-how-to-tell-pushdown-computation.md).|
+|<a name="tf6408"></a>**6408**|Enables visibility of the estimated execution plan to see the remote query plan of PolyBase pushdown computation. <br /><br />**Note:** This trace flag applies to [!INCLUDE[sssql19](../../includes/sssql19-md.md)], and higher builds. For more information, see [How to tell if external pushdown occurred](../../relational-databases/polybase/polybase-how-to-tell-pushdown-computation.md).<br /><br />**Scope**: global or session or query (QUERYTRACEON)|
 |<a name="tf6498"></a>**6498**|Enables more than one large query compilation to gain access to the big gateway when there is sufficient memory available. This trace flag can be used to keep memory usage for the compilation of incoming queries under control, avoiding compilation waits for concurrent large queries. It is based on the 80 percentage of SQL Server Target Memory, and it allows for one large query compilation per 25 gigabytes (GB) of memory. For more information, see this [Microsoft Support article](https://support.microsoft.com/kb/3024815).<br /><br />**Note:** Starting with [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] SP2 and [!INCLUDE[sssql16-md](../../includes/sssql16-md.md)] this behavior is controlled by the engine and trace flag 6498 has no effect.<br /><br />**Scope**: global only|
 |<a name="tf6527"></a>**6527**|Disables generation of a memory dump on the first occurrence of an out-of-memory exception in CLR integration. By default, [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] generates a small memory dump on the first occurrence of an out-of-memory exception in the CLR. The behavior of the trace flag is as follows:<br /><ul><li>If this is used as a startup trace flag, a memory dump is never generated. However, a memory dump may be generated if other trace flags are used. <li>If this trace flag is enabled on a running server, a memory dump will not be automatically generated from that point on. However, if a memory dump has already been generated due to an out-of-memory exception in the CLR, this trace flag will have no effect.</li></ul><br />**Scope**: global only|
 |<a name="tf6532"></a>**6532**|Enables performance improvement of query operations with spatial data types in [!INCLUDE[ssSQL11](../../includes/sssql11-md.md)] and [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)]. The performance gain will vary, depending on the configuration, the types of queries, and the objects. For more information, see this [Microsoft Support article](https://support.microsoft.com/kb/3107399).<br /><br />**Note:** Starting with [!INCLUDE[sssql16-md](../../includes/sssql16-md.md)] this behavior is controlled by the engine and trace flag 6532 has no effect.<br /><br />**Scope**: global and session|