reporting on a DTS performance reporting

[sumGirl]

Hi all. I have a dts package called package1 that I run once a week
that does some imports/queries against about the same amount of data
each run. I am wondering (hoping!) if I can run a query that will show
its performance over the past 6 months in terms of how long the
execution for each run took.

I think SQL server saves this dts package run history somewhere and if
so how can I do this? Am I totally off base?

[Simon Hayes]

"sumGirl" <em*****@netscape.net> wrote in message
news:a5**************************@posting.google.c om...

Hi all. I have a dts package called package1 that I run once a week
that does some imports/queries against about the same amount of data
each run. I am wondering (hoping!) if I can run a query that will show
its performance over the past 6 months in terms of how long the
execution for each run took.

I think SQL server saves this dts package run history somewhere and if
so how can I do this? Am I totally off base?

If you scheduled it as a scheduled job, then you can look at the job history
in msdb..sysjobhistory. If you also enabled package logging to MSSQL, you
can check out the msdb..sysdtssteplog table, which has start and end time
columns, as well as elapsed time.

Simon