vendredi 23 janvier 2015

How to identify where a package execution has spent most of the time?


Team BI has a package deployed as a project on SQL Server 2012.


How can I find how long a package takes to run on a daily basis, and where it has spent most of the time?


I know that the catalog.executions view can be queried, anything else?


I am getting this request from developers:




Today’s BI Incremental ran without error but took far longer than usual. The Sales Incremental took 1hour 12mins. Yesterday it took 15 mins. There has been no release/code changes.


The Sales ETL hits databasename on servername. Was there something going on at the time of the load (5am)? Anything logged?




enter image description here


enter image description here





Aucun commentaire:

Enregistrer un commentaire