Update dbcc-traceon-trace-flags-transact-sql.md

Author: pmasl

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

@@ -117,7 +117,7 @@ The following table lists and describes the trace flags that are available in [!
 |**4138**|Causes [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] to generate a plan that does not use row goal adjustments with queries that contain TOP, OPTION (FAST N), IN, or EXISTS keywords. For more information, see this [Microsoft Support article](https://support.microsoft.com/kb/2667211).<br /><br />Starting with [!INCLUDE[ssSQL15](../../includes/sssql15-md.md)] SP1, to accomplish this at the query level, add the USE HINT 'DISABLE_OPTIMIZER_ROWGOAL' [query hint](../../t-sql/queries/hints-transact-sql-query.md) instead of using this trace flag.<br /><br />**Note:** Please ensure that you thoroughly test this option, before rolling it into a production environment.<br /><br />**Scope**: global or session or query| 
 |**4139**|Enable automatically generated quick statistics (histogram amendment) regardless of key column status. If trace flag 4139 is set, regardless of the leading statistics column status (ascending, descending, or stationary), the histogram used to estimate cardinality will be adjusted at query compile time. For more information, see this [Microsoft Support article](https://support.microsoft.com/kb/2952101).<br /><br />Starting with [!INCLUDE[ssSQL15](../../includes/sssql15-md.md)] SP1, to accomplish this at the query level, add the USE HINT 'ENABLE_HIST_AMENDMENT_FOR_ASC_KEYS' [query hint](../../t-sql/queries/hints-transact-sql-query.md) instead of using this trace flag.<br /><br />**Note:** Please ensure that you thoroughly test this option, before rolling it into a production environment.<br /><br />**Note:** This trace flag does not apply to CE version 70. Use trace flags 2389 and 2390 instead.<br /><br />**Scope**: global or session or query|
 |**4199**|<a name="4199"></a>Enables query optimizer (QO) fixes released in [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Cumulative Updates and Service Packs.<br /><br />QO changes that are made to previous releases of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] are enabled by default under the latest database [compatibility level](../../t-sql/statements/alter-database-transact-sql-compatibility-level.md) in a given product release, without trace flag 4199 being enabled.<br /><br />The following table summarizes the behavior when using specific database compatibility levels and trace flag 4199. For more information, see this [Microsoft Support article](https://support.microsoft.com/kb/974006).<br /><br /><table border="1" frame="void" width="550"><tr valign="middle" align="center"><td>**Database compatibility level**</td><td>**TF 4199**</td><td>**QO changes from previous database compatibility levels**</td><td>**QO changes for current version post-RTM**</td></tr><tr valign="middle" align="center"><td rowspan="2">**100 to 120**</td><td>Off</td><td>Disabled</td><td>Disabled</td></tr><tr valign="middle" align="center"><td>On</td><td>Enabled</td><td>Enabled</td></tr><tr valign="middle" align="center"><td rowspan="2">**130**</td><td>Off</td><td>Enabled</td><td>Disabled</td></tr><tr valign="middle" align="center"><td>On</td><td>Enabled</td><td>Enabled</td></tr><tr valign="middle" align="center"><td rowspan="2">**140**</td><td>Off</td><td>Enabled</td><td>Disabled</td></tr><tr valign="middle" align="center"><td>On</td><td>Enabled</td><td>Enabled</td></tr><tr valign="middle" align="center"><td rowspan="2">**150**</td><td>Off</td><td>Enabled</td><td>Disabled</td></tr><tr valign="middle" align="center"><td>On</td><td>Enabled</td><td>Enabled</td></tr></table><br /><br />Starting with [!INCLUDE[ssSQL15](../../includes/sssql15-md.md)], to accomplish this at the database level, see the QUERY_OPTIMIZER_HOTFIXES option in [ALTER DATABASE SCOPED CONFIGURATION &#40;Transact-SQL&#41;](../../t-sql/statements/alter-database-scoped-configuration-transact-sql.md).<br /><br />Starting with [!INCLUDE[ssSQL15](../../includes/sssql15-md.md)] SP1, to accomplish this at the query level, add the USE HINT 'ENABLE_QUERY_OPTIMIZER_HOTFIXES' [query hint](../../t-sql/queries/hints-transact-sql-query.md) instead of using this trace flag.<br /><br />**Scope**: global or session or query|
-|**4610**|Increases the size of the hash table that stores the cache entries by a factor of 8. When used together with trace flag 4618 increases the number of entries in the TokenAndPermUserStore cache store to 8,192. For more information, see this [Microsoft Support article](https://support.microsoft.com/kb/959823).<br /><br />**Scope:** global only|
+|**4610**|Increases the size of the hash table that stores the cache entries by a factor of 8. When used together with trace flag 4618 increases the number of entries in the TokenAndPermUserStore cache store to 8,192. For more information, see this [Microsoft Support article](https://support.microsoft.com/kb/959823) and this [Microsoft Support article](https://support.microsoft.com/kb/955644).<br /><br />**Scope:** global only|
 |**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|
 |**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, see this [Microsoft Support article](https://support.microsoft.com/kb/959823).<br /><br />**Scope:** global only|
 |**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|