Skip to content

Commit 50acaca

Browse files
authored
Merge pull request #6856 from SeanGallardy/patch-21
Updated TF 6534
2 parents b8a2ca0 + d7594d6 commit 50acaca

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -143,7 +143,7 @@ The following table lists and describes the trace flags that are available in [!
143143
|<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|
144144
|<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|
145145
|<a name="tf6533"></a>**6533**|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 6533 has no effect.<br /><br />**Scope**: global and session|
146-
|<a name="tf6534"></a>**6534**|Enables performance improvement of query operations with spatial data types in [!INCLUDE[ssSQL11](../../includes/sssql11-md.md)], [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] and [!INCLUDE[sssql16-md](../../includes/sssql16-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 />**Scope**: global only|
146+
|<a name="tf6534"></a>**6534**|Enables performance improvement of query operations with spatial data types beginning with [!INCLUDE[ssSQL11](../../includes/sssql11-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 />**Scope**: global only|
147147
|<a name="tf6545"></a>**6545**|Enables CLR strict security. For more information, see this [Microsoft Support article](https://support.microsoft.com/kb/4018930).<br /><br />**Note:** This trace flag applies to [!INCLUDE[ssSQL11](../../includes/sssql11-md.md)] SP3 CU10, [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] SP2 CU6, [!INCLUDE[sssql16-md](../../includes/sssql16-md.md)] RTM CU7, [!INCLUDE[sssql16-md](../../includes/sssql16-md.md)] SP1 CU4, and higher builds. Starting with [!INCLUDE[ssSQL17](../../includes/sssql17-md.md)] this feature is enabled by default and trace flag 6545 has no effect.<br /><br />**Scope**: global only|
148148
|<a name="tf7314"></a>**7314**|Forces NUMBER values with unknown precision/scale to be treated as double values with OLE DB provider. For more information, see this [Microsoft Support article](https://support.microsoft.com/kb/3051993).<br /><br />**Scope**: global and session|
149149
|<a name="tf7412"></a>**7412**|Enables the lightweight query execution statistics profiling infrastructure. For more information, see this [Microsoft Support article](https://support.microsoft.com/kb/3170113).<br /><br />**Note:** This trace flag applies to [!INCLUDE[sssql16-md](../../includes/sssql16-md.md)] SP1 and higher builds. Starting with [!INCLUDE[sql-server-2019](../../includes/sssql19-md.md)] this trace flag has no effect because lightweight profiling is enabled by default.<br /><br />**Scope**: global only|

0 commit comments

Comments
 (0)