Microsoft® SQL Server® 2012 Bible

(Ben Green) #1

946


Part VII: Monitoring and Auditing


There is a small performance hit for using Change Tracking, but it’s a lightweight feature
with about the same performance hit as adding an index. The performance cost depends on
the size of the primary key and the number of rows affected by the transaction. A single
column integer primary will have less performance cost than a wide composite primary key.
Adding column tracking also adds to the performance overhead.

Confi guring Change Tracking


Compared to other optional SQL Server technologies, Change Tracking is relatively easy to
turn on and confi gure. It’s simply turned on for the database and then for each table.

Enabling the Database
Change Tracking may be enabled for the database in Object Explorer’s Database Properties
dialog, available from each database’s context menu (as shown in Figure 41-1). Changing the
values in the drop-down boxes immediately changes the database settings when you close
the properties dialog.

FIGURE 41-1
The Database Properties’ Change Tracking page displays the current settings and may be
used to enable or disable Change Tracking.

c41.indd 946c41.indd 946 7/31/2012 10:17:20 AM7/31/2012 10:17:20 AM


http://www.it-ebooks.info
Free download pdf