eG Help

Packages are at the core of the data transformation and integration services provided by SSIS. Using packages, you can merge data from heterogeneous data sources into the SQL server. Packages also help populate data warehouses, clean and standardize data, and automate administrative tasks.

This means that if a package runs slowly, it will adversely impact the operations and overall performance of the data integration and workflow applications that are built on the SSIS platform. To avoid such performance setbacks, administrators need to track the execution time of individual packages, rapidly isolate packages that are executing slowly, and quickly diagnose and fix the reason for the delay. This is where the MSSQLISPacTest test helps!

This test monitors the packages that are deployed to the SQL Integration server and tracks the execution time of each package. Packages that have been executing beyond an acceptable duration (which is configurable) are promptly captured and brought to the attention of administrators as part of detailed diagnostics. This is how the test highlights ‘slow packages’. Additionally, the test sheds light on what could have slowed down package execution. Typically, any slowness in package execution can be attributed to delays in the operations of the components (eg., data flow components, control flow components etc.) that are included in that package. This is why, the test not only monitors package execution, but also measures the amount of time the components in each package took to execute. If one/more components have taken longer than a permitted duration (which is configurable) to execute, then the detailed diagnostics reported by the test pinpoints such components. Using these detailed metrics, administrators can quickly and easily determine the rootcause of package slowness.

Measurement	Description	Measurement Unit	Interpretation
componentCount	Indicates the number of components running on the server.	Number
maxDurationOfComponent	Indicates the high watermark of execution duration across components.	Seconds	If the value of this measure is abnormally high, it implies that one/more components are running for a duration beyond the Execution Duration configured for this test. In such a situation, use the detailed diagnosis of this measure to know which components are running slowly, and which package they belong to.
packageCount	Indicates the number of packages running on the server.	Number
maxDurationOfPackage	Indicates the high watermark of execution duration across packages.	Seconds	If the value of this measure is abnormally high, it implies that one/more packages are running for a duration beyond the Execution Duration configured for this test. In such a situation, use the detailed diagnosis of this measure to know which packages are running slowly, and which components in those packages are contributing to the delayed execution.