Performance Counters

Performance Counters

 

Integration Services installs a set of performance counters that you can use to monitor the performance of the data flow engine. For example, you can watch the "Buffers spooled" counter to determine whether data buffers are being written to disk temporarily while a package is running. This swapping reduces performance and indicates that the computer has insufficient memory.

System_CAPS_ICON_note.jpg Note


If you install Integration Services on a computer that is running Windows Server 2003, and then upgrade that computer to Windows Server 2008, the upgrade process removes the Integration Services performance counters from the computer. To restore the Integration Services performance counters on the computer, run SQL Server Setup in repair mode.

The following table describes the performance counters.

Performance counterDescription
BLOB bytes readThe number of bytes of binary large object (BLOB) data that the data flow engine has read from all sources.
BLOB bytes writtenThe number of bytes of BLOB data that the data flow engine has written to all destinations.
BLOB files in useThe number of BLOB files that the data flow engine currently is using for spooling.
Buffer memoryThe amount of memory that is in use. This may include both physical and virtual memory. When this number is larger than the amount of physical memory, the Buffers Spooled count rises as an indication that memory swapping is increasing. Increased memory swapping slows performance of the data flow engine.
Buffers in useThe number of buffer objects, of all types, that all data flow components and the data flow engine is currently using.
Buffers spooledThe number of buffers currently written to the disk. If the data flow engine runs low on physical memory, buffers not currently used are written to disk and then reloaded when needed.
Flat buffer memoryThe total amount of memory, in bytes, that all flat buffers use. Flat buffers are blocks of memory that a component uses to store data. A flat buffer is a large block of bytes that is accessed byte by byte.
Flat buffers in useThe number of flat buffers that the Data flow engine uses. All flat buffers are private buffers.
Private buffer memoryThe total amount of memory in use by all private buffers. A buffer is not private if the data flow engine creates it to support data flow. A private buffer is a buffer that a transformation uses for temporary work only. For example, the Aggregation transformation uses private buffers to do its work.
Private buffers in useThe number of buffers that transformations use.
Rows readThe number of rows that a source produces. The number does not include rows read from reference tables by the Lookup transformation.
Rows writtenThe number of rows offered to a destination. The number does not reflect rows written to the destination data store.

You use the Performance Microsoft Management Console (MMC) snap-in to create a log that captures performance counters.

For information about how to improve performance, see Data Flow Performance Features.

For Integration Services projects that are deployed to the Integration Services server, you can obtain performance counter statistics by using the dm_execution_performance_counters (SSISDB Database) function.

In the following example, the function returns statistics for a running execution with an ID of 34.

select * from [catalog].[dm_execution_performance_counters] (34)

In the following example, the function returns statistics for all the executions running on the Integration Services server.

select * from [catalog].[dm_execution_performance_counters] (NULL)


System_CAPS_ICON_important.jpg Important


If you are a member of the ssis_admin database role, performance statistics for all running executions are returned. If you are not a member of the ssis_admin database role, performance statistics for the running executions for which you have read permissions, are returned.

Execution of Projects and Packages

Show:
© 2016 Microsoft