Skip to content

Latest commit

 

History

History
37 lines (32 loc) · 1.98 KB

File metadata and controls

37 lines (32 loc) · 1.98 KB
title Logged vs. Unlogged Modifications | Microsoft Docs
ms.custom
ms.date 03/14/2017
ms.prod sql
ms.prod_service database-engine, sql-database, sql-data-warehouse, pdw
ms.reviewer
ms.technology native-client
ms.topic reference
helpviewer_keywords
text columns [ODBC]
SQL Server Native Client ODBC driver, image columns
SQL Server Native Client ODBC driver, text columns
data types [ODBC], image
data types [ODBC], text
logged vs. nonlogged modifications [SQL Server Native Client]
columns [ODBC]
ODBC data types, image columns
nonlogged vs. logged modifications
ODBC data types, text columns
image columns [ODBC]
ms.assetid 20aa5b27-4a2c-46e7-8356-beb0eebf4b7e
author markingmyname
ms.author maghan
monikerRange >=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-server-2016||=sqlallproducts-allversions||>=sql-server-linux-2017||=azuresqldb-mi-current

Logged vs. Unlogged Modifications

[!INCLUDEappliesto-ss-asdb-asdw-pdw-md]

An application can request that the [!INCLUDEssNoVersion] Native Client ODBC driver not log text, ntext, and image modifications. Care should be used with this option, however. It should be used only for those situations where the text, ntext, or image data is not critical and data owners are willing to trade off the ability to recover data for higher performance.

The logging of text, ntext, and image modifications is controlled by calling SQLSetStmtAttr with the Attribute parameter set to SQL_SOPT_SS_ TEXTPTR_LOGGING and ValuePtr set to either SQL_TL_ON or SQL_TL_OFF.

See Also

Managing Text and Image Columns