We have noticed in our environment slowness when starting SSIS packages from SQL Server jobs. I did a quite detailed study on when the slowness actually occurs and what are the consequences. Here are the results.
The SSIS package execution is slow if all the following is true:
The package is started from a job. If started directly as a SSIS package, the execution is fast.
The job is running on a 64 bit Windows Server (SQL Server 2005 SP2). The SSIS package andÃÂ the job are either on the same serverÃÂ or on different servers (the second server is SQL Server 2005 SP1).ÃÂ If the job is run on a 32-bit workstation (Windows XP SP2) the execution is fast (the SSIS package still being on the server).
The package contains tasks.
ÃÂ§ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ If there are no tasks, just an empty sequence container, the execution is fast.
ÃÂ§ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ If a package that has no tasks has logging into the database configured, the execution is fast.
ÃÂ§ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ Slowness has been verified with A) a package having a single Execute SQL statement and B) a package having a Send Mail task.
It doesn't seem to matter which user account is used on when running the job.
The slowness happens in several locations, e.g. (there are also others, at least the following have been verified)
There is exactly 30 seconds lag between starting the job (as seen from job history) and when PreValidate (as seen in the sy
View Complete Post