.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
david stephan
Gaurav Pal
Post New Web Links

Slow startup of SSIS package if started using a SQL Server job

Posted By:      Posted Date: September 07, 2010    Points: 0   Category :Sql Server
Hello all,   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

More Related Resource Links

SSIS package runs very slow on SQL 2008 R2 server, runs very quickly on virtual XP machine


Hi All,

I've been troubleshooting this issue on and off for a few weeks now.  I've scoured these forums and looked through sqlis.com, but I'm just about out of ideas.  Here's what's happening.

I have a *very* simple integration services package I developed on a  virtual Windows XP machine running on my workstation.  The package uses a script task to simulate a one-row source with four columns (int, char(64), varchar(512) and char(2)) and then passes that off to a fuzzy lookup.  The fuzzy lookup is running against a table of only about 6,000 rows.  The package then inserts the results into a table and exits.

When I run this from my virtual XP machine, it completes in 1-2 seconds.

When I execute this on the server (either as a job or through DTExec) it takes 14-18 seconds.  The server stores the package in MSDB and is also the location where the fuzzy lookup happens.

I've tried using the 32-bit runtime, creating 32- and 64-bit aliases to the server, changing the name of the server from the name to the IP address and port, stopping/restarting SQL Agent and SSIS Services... none of this seems to change the execution time.

The one thing I've found is that if I enable package logging on the logging tab of the job, using the SSIS Log Provider for SQL Server and pointing it to the same connection st

Execute SSIS PAckage on Remote Server

I've seen several posts pertaining to this topic, but none of them covers what I'm having an issue with. I'm trying to create a "master job server". Essentially, I want to control all maintenance jobs from one central location. I've created SSIS packages that handle full backups, transaction log backups, index rebuilding, etc. on all of my production boxes. I've stored those packages in SQL Server. What I'd like to do now is create a separate job for each of those tasks on one central SQL Server and run those packages from there. I've been successful in creating a test job. The only step in the job is an SSIS PAckage execution step. The step successfully found the package I want to execute on the target server. When the job ran, I got the follwoing error: The job failed.  Unable to determine if the owner (ADMINSYS\arobinsf) of job SFO2PQE03 - Database Backup (FULL) has server access (reason: Could not obtain information about Windows NT group/user 'ADMINSYS\arobinsf', error code 0x2751. [SQLSTATE 42000] (Error 15404)). I want to make sure this job is executing on the remote server and not trying to execute locally. Is there something I'm missing in the set up of this job? I should also mention that the SSIS packages were created in SQL2K5, but I'm executing them from SSMS for SQL2K8. Any help would be appreciated! Thanks! A. M. Robinson

SSIS Package working on SQL Client Machine but when trying to run on SQL Server machine giving error

Hi We are trying to run SSIS package on sql server machine but sometimes it is giving error for data flow task containing Script Component. Error is - [SSIS.Pipeline] Error: component "SCR DimensionRelation" (1) failed the post-execute phase and returned error code 0x80004002. This error is not coming continuously. And also not for specific DFT. It comes for different DFTs as we rerun the package. Can anybody help me on this? We are using SQL server 2008. We are not getting any error on client machine :(:(

Loading Decimal Number From Excel into SQL Server 2005 using SSIS Package

If you have an excel spreadsheet that displays a number .02 (because it is formated) but internally it is stored as .2654329 and you want to load .2654329 how can you do that in the SSIS package?  When we load the spreadsheet it is loading .02.  Is there some kind of option in the SSIS package to tell the package to load the internal number?lcerni

How to create a SSIS package to import records form SQl Server 2008 tables to text files

I am a newbie to SSIS and would like to create a package to accomplish the task referenced in the above title. Will appreciate any links and pointers in the right direction.   Thanksakoranteng

SSIS package fails under SQL Server Agent job


Hi All

I have designed a SSIS package to encrypt a file using Cipher (EFS) it works fine from BIDS & Package Execution Utility.

But SQL Server Agent job is failing to do this. I am getting the error as

" In executing C:\Windows\System32\Cipher.exe /e /a C:\Test.txt at "",The Process Exit code was 1 while the expected was 0." 


Please help me.




SSIS Package for Delta Data between Oracle and SQL Server


Hi all

I have BI Server and Tables and Data Populated using SSIS package.Now Data is ready in BI server.Next week Ihave to same excersize to filll the Data(DROP tables,CREATE table and Pump the Data)

Can any body give an idea how to create SSIS package which can pupm the Delta Data Oracle and SQL Server.


Thanks in advance




SSIS 2K5 - Deploy package with C# - Really Slow



For a DataWareHouse project, I did an WIX  install manager to Create à DataWareHouse, Deploy SSIS package and Deploy a OLAP cube.

When It come to deploy (load) dtsx package, it takes about 40-60 secondes to load each package (I have around 50 packages so its really too long)

This is the code i'm using :

	    DirectoryInfo di = new DirectoryInfo(session["INSTALLLOCATION"] + @"Sources");
        FileInfo[] rgFiles = di.GetFiles("*.dtsx");
        Microsoft.SqlServer.Dts.Runtime.Application app = new Microsoft.SqlServer.Dts.Runtime.Application();
        foreach (FileInfo fi in rgFiles)
          string pkg = session["INSTALLLOCATION"] + @"Sources\" + fi.Name + "";
 		 Package p = app.LoadPackage(pkg, null); //THIS TAKE 40-60 SECONDE TO EXECUTE       


SSIS package on standalone server invoked by SQL Server Agent raises DTS_E_PRODUCTLEVELTOLOW


I have developed an SSIS 2005 package but the client was reluctant to install SSIS on their SQL Server and instead installed it (SSIS) on an IIS server which doesn't have SQL Server on it all. Microsoft documentation surprisingly indicated this would work. http://technet.microsoft.com/en-gb/library/cc966389.aspx states "SSIS packages can also be run on systems where SQL Server is not installed. However, the .NET Framework and the SSIS runtime must be installed in order to execute the packages on systems that do not have SQL Server 2005 installed."

The package can be run from within BIDS and by invoking from the SSIS server fine and runs to completion. It fails when invoked by the SQL Server Agent on the actual SQL Server (i.e. NOT the SSIS server) (which IS Enterprise version) and raises a DTS_E_PRODUCTLEVELTOLOW error. This is the third "step" out of three and is a fairly basic data flow task where the results of a SQL Server proceedure are output to a text file.

I have logging on which doesn't tell me anything more than I already knew
OnError,<ServerName>,<SQLServerAgentUser>,<PackageName>,{C88F42DE-E3A8-40CB-A140-F10E270C5F1F},{1D2B421E-E067-4458-A908-23C7F081EF28},9/30/2010 4:52:21 PM,9/30/2010 4:52:21 PM,-1073450754,0x,

SSIS packages run slow under Execute Package Utility


I have developed a dtsx package to load data from xml load table into a dozen of flat tables. I found the SSIS is running slow (almost 10 times slower) under Execute Package Utility than running under visual studio IDE.

Does anyone have same experience?


SQL Agent - Running SSIS Package - Windows Server 2008/Windows 7 - Messenger Services


We have tried to run a SQL job for SSIS Package. But it failed during the execution with the error "[364] The Messenger service has not been started - NetSend notifications will not be sent". But in the job, no notifications have been configured and in windows server 2008/Windows-7 there is no messenger service at all.

When we search for the the messenger service in windows 7/windows server 2008, we found that service is not in both the OS and it was replaced by msg.exe. 

Any help or workaround would be appreciated.

Thanks in advance.

PS: The normal SQL jobs other than SSIS are working fine without any error.

Vijay Pandurangan

Which edition of sql server for SSIS package development



which is the minimum edition of sql server which will allow me to develop ssis in BIDS and execute them.

I use to pull data from oracle by means of some simple transactions and populate them in Sql Server

SSIS Package Logging of Errors to Sql Server


SSIS 2008 R2

I’m a relative newbie to SSIS but a long time developer / dba.  I have developed several  packages that I execute from stored procedures, via the cmdshell,  and I want to capture any error messages that come from the actual execution.  Ideally I would check a sql table for any error results.  I found  SSIS > Logging on the Menu bar and created a Sql Server log (in the same database as I am executing the sp from).  In the Configure SSIS Logs, I created the appropriate entry on the Providers and Logs tab and on the details tab I selected only the OnError check box.  All well and good.  After an execution I find the sysssislog table in the system tables.  What I did not expect to see was the Begin Execution / End Execution rows for the package just executed.  I only want errors to show up however I have not yet tested an error situation.

Savng SSIS package might fail with "Library not registered" after you install SQL Server 2005 SP2


After installing SQL Server 2005 SP2 you try to change the SSIS package and when you try to save it. it might fail with the below message:

- File - save copy of package
- Package  location = SSIS package store
-Server - <instance name>
- Aunthentication = windows authentication
- gave the package path
- Under Protection level - REly on server storage and roles for access control
- Wehn we click on OK it fails with:
Library not registered. (Exception from HRESULT: 0x8002801D (TYPE_E_LIBNOTREGISTERED)) (Microsoft.SqlServer.DTSRuntimeWrap)"

Error details:

Library not registered. (Exception from HRESULT: 0x8002801D (TYPE_E_LIBNOTREGISTERED)) (Microsoft Visual Studio)

Program Location:

   at Microsoft.SqlServer.Dts.Runtime.Application.SaveToDtsServer(Package pPackage, IDTSEvents pEvents, String sPackagePath, String sServerName)
   at Microsoft.DataTransformationServices.Controls.PackageLocationControl.SavePackage(Package package)
   at Microsoft.DataTransformationServices.Design.Controls.PackageSaveCopyForm.PackageSaveCopyForm_FormClosing(Object sender, FormClosingEventAr

SSIS package which reads excel files fails on SQL Server Agent



I have a SSIS package which reads an excel file and loads data into a table using script component(C#) as a source. The package runs without any errors when I manually run it on my machine and on the server. But the package fails when run as a SQL Server Agent job.

I tried all the possible fixes I found on the web but still can't get it to work.

Could you shed some light on it?



Schedule problem with SSIS package on SQL Server 2008

Hello there

Step 1 - I created my first SSIS package (simple ole db source to file destination scenario) in BIDS 2008. I created and run this on the SQL Server 2008 - SP1(on Win2k3 SP2 - 64 bit machine). This integratin scenario creates a flat file with some records in it (records modified today). This packages runs ok from BIDS.

Step 2- After deploying this SSIS package to the SQL Server 2008, I was able to run it successfully. The package created a flat file with some records.

On the two occasions above, the ssis package did exactly what I wanted it to do.

I tried to create SQL Server Agent job selected the Type as SSIS package, allowed this package to run under Windows Authentication (service account - same account used as in Steps 1 & 2). Before scheduling, I thought why not run this manually. The job ran successfully (looked at the success message and the history of the job), but a flat file was created (as expected) without any records (not as expected!)

Please note I have tried the default protection level ("EncryptSensitiveWithUserKey") as well as ("DontSaveSensitive") on the package.

I am suspecting that when the SSIS package is scheduled the SQL Server Agent is unable to pass the authentication to the SSIS package !?

Some help will be appreciated.

ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend