Performance problem loading packages

We're having a performance problem with a package since an error occurred. The original error came from the Job Manager whicj was unable to start a thread. Our understanding is that this is a memory related issue and we'll deal with that.

What is realy odd is what happened after that. The package executes from a SQL Agent job that includes 3 other packages. Each package is stored on the file system. Package execution time for the affected package changed from less than a minute to over 5 minutes. The other packages continued to execute normally.

In checking the logs there is large time gap between the start of the SQL Agent step and the first pre-validation message that accounts for 4 minutes, as if there is some issue in loading the package. The issue is ongoing. Does anyone know what happens between the start of the SQL Agent job and the first prevalidate message? Is this some type of caching issue?

SQL Agent step starts at 4:05:27

First Prevalidate message: 4:09:24

Package Execution start: 4:09:57

End Execution 4:10:59

thanks

Peter

Rebooting the server fixed the immediate problem.

Performance problem

HI, I have a performance problem with one of my set of packages. They run fine on dev machine but much slower on test server which has twice (8gb) the memory of my dev server (4gb). The first time I run the set of package they execute in less than a minute which is normal. But subsequent executions in same conditions (tables are empty) takes 2-3 minutes. When I restart Sql server 2005, the loading time is back to less than a minute.

I enables the "use awe" for memory beyond 4 gb on test server and while executing, total memory is far beyond the 8gb of test server and on the four available processors, only one seems to be used. Also, deployment on other machines have no problems. We rebuilt the test server (re-installed windows, Sql server 2005, SP1 and patches) with no luck.

I would like to monitor the problem using performance monitor and Sql server profiler, is there some specific counters or trace events that I should focus on? My set of packages (one main package calling several execute package tasks) load approximately 100K lines and they are deployes on file system.

Thank you,
Ccote

Not sure about the cause of your problem. I would sugest to enable package logging and compare execution logs between server and try to identify possible botle necks.

Also there is an interesting document about performance tunning:

http://download.microsoft.com/download/1/3/4/134644fd-05ad-4ee8-8b5a-0aed1c18a31e/SSISPerfTuning.doc