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

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

SSIS packages run slow under Execute Package Utility

Posted By:      Posted Date: October 02, 2010    Points: 0   Category :Sql Server

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?


View Complete Post

More Related Resource Links

Execute SSIS Package PART based on Some Condition

Hello, Is it possible to execute part of the Package based some condition? (Like If var1 = true, then execute this block). If Yes, what control flow I should use. Please advse. I will have a Package Variable and if that variable is True then some part should execute. REst all should execute every time the package is called. Like if I will have "2 Sequence Container" in my control flow, the first one should execute every time, but 2nd one only if the variable value = True. Thanks, Prabhat

Execute an SSIS package from ASP.net (C#) - my package keeps failing. Help! - Works on localhost but

I'm looking for any and all information on how to execute an SSIS package from my asp.net web site. I have written the call and when I run the application from (Localhost) it works, but when I run it from the server it does not.Here is my code to call and execute the package: public string ProcessFiles(int ClientID, string FileName) { //System.Security.Principal.WindowsImpersonationContext impersonationcontext; //impersonationcontext = ((System.Security.Principal.WindowsIdentity)ServiceContext.User.Identity).Impersonate(); string packagePath = "\\\\\\Customer File Import.dtsx"; Microsoft.SqlServer.Dts.Runtime.Application app; Microsoft.SqlServer.Dts.Runtime.Package pkg; Microsoft.SqlServer.Dts.Runtime.Variables vars; Application integrationServices = new Application(); DTSExecResult result; FileName = FileName.Substring(FileName.Length - 25 , 25); app = new Microsoft.SqlServer.Dts.Runtime.Application(); pkg = app.LoadPackage(packagePath, null); //pkg = integrationServices.LoadFromSqlServer("Customer File Import.dtsx", "", "healthtech\\brian.montfort", "Nightdragon8", null); vars = pkg.Variables; if (pkg.Variables.Contains("

Execute SSIS package stored in Database - From Stored Procedure

Dear frnds, I am trying to execute a SSIS package that is stored in a SQL Server 2005 database Want to execute from a stored procedure in same database.  What commands/operations are necessary ? I am also having Two parameter. Regards, sajid 

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

How to Create SSIS Package to RUN the preweblog utility exe for IIS Logfiles

Hello ,                   I need to create SSIS Package for Microsoft tool  preweblog utility.exe to modify the IIS LogFiles. Kindly provide me some information related to it.

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

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

SSIS package is giving error when ran thru JOB...its running good when I execute in BI Studio or Exe

Friends I am getting weird issue...I built an SSIS package. In one variable I used express builder and built like this... RTRIM( (DT_STR, 2,1252)  (((DT_I4) ( (DT_WSTR, 3) (SUBSTRING( @[system::machineName] , 12, 16 ))) +1) /2)) when I run the package outside ie., with VStudio or execute utility it running absolutely with out any problem. But when I created a job just to execute that package in particular timings...the job is totally failing by throwing error....the error output is like the following: Started:  10:22:33 AM Error: 2010-02-27 10:23:06.23    Code: 0xC00470C2    Source: Rerun_MissingFiles    Description: Error code 0x80020005 occurred attempting to convert from data type DT_WSTR to data type DT_I4. Error: 2010-02-27 10:23:06.23    Code: 0xC00470C4    Source: Rerun_MissingFiles    Description: Casting expression "(SUBSTRING( @[system::machineName] , 12, 16 )))" from data type "DT_WSTR" to data type "DT_I4" failed with error code 0xC00470C2. End Error Can any one help me please? Thanks in advance.

Implementing Transaction in SSIS Package - [Execute SQL Task] Error: Failed to acquire connection "<

I have a simple SSIS package with three "Execute SQL Tasks". I am using ADO.Net Connection to execute SPs on a DB server. When I execute this package It works fine. So far so good. Now, I need to implement transation on this package. And problem starts now onwards. When I try to execute package after setting TransationOption = Required for the Sequence container which contains all the tasks, I get following error. [Execute SQL Task] Error: Failed to acquire connection "NYCDB0008.Export". Connection may not be configured correctly or you may not have the right permissions on this connection. "NYCDB0008.Export" is the name of the ADO.Net connection. I have been hunting for any solution but all in vain. I have tried changing all DTC settings on the dev as well as Database server. Please respond if anyone has any solution. Thanks! Anand

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       


how do i do a minimal client tool install to execute SSIS packages


I am trying to migrate our processing from command line based scripts and foxpro to SQL so I need to run the SSIS packages using dtexec. I copied the dtexec file and a few dll's that are missing to our production servers but i cant execute the packages. I dont want to install the full client tools (particularly managment/business inteligence studio) on our production servers due to the overhead and limited system disk space.

Can somebody tell me what the minimum install would be so I would be able to run SSIS packages using the dtexec or dtexecui tools? I would also like to install some of the other command line client tools like osql etc.

execute SSIS Package


I built an SSIS package using BIDS and saved it on a server.  I have other users of the DB that use SQL 2010 express. What I would like to know the easiest, or maybe the best way, to execute that package using SQL 2010 express? 

If anyone can point me in the right direction that would be great!


SSIS - on execute package "out of memory " error



when i am trying to execute package in ssis then given below errors comes many times.how to fix it.any body can ......

in ssis default buffer size 10 mb.

soure is iseries-db2 on as400 in production server ,

 and destination is db2 udb on windows in dev server.

usersapce page size in db2 is 16-32k

4 gb ram support in server with 2003 server standard edition.

errors are---

Information: 0x4004800D at CHDRPF 312-315, DTS.Pipeline: The buffer manager failed a memory allocation call for 15728400 bytes, but was unable to swap out any buffers to relieve memory pressure. 3 buffers were considered and 3 were locked. Either not enough memory is available to the pipeline because not enough are installed, other processes were using it, or too many buffers are locked.
Error: 0xC0047012 at CHDRPF 312-315, DTS.Pipeline: A buffer failed while allocating 15728400 bytes.
Error: 0xC0047011 at CHDRPF 312-315, DTS.Pipeline: The system reports 83 percent memory load. There are 3488509952 bytes of physical memory with 558743552 bytes free. There are 2147352576 bytes of virtual memory with 222920704 bytes

SSIS Package fails with Execute Process Task when run from SQL Agent Job


I have an SSIS 2008 package running on Win 2008 64-bit server. The package has an Execute Process Task that runs a net use command using cmd.exe to make a connection.

This runs successfully when tested from the command prompt and runs successfully when the package is run in Visual Studio 2008. However, when the package is called from a SQLAgent job the package fails with the error (actual servernames and passwords removed):

Failing Task Name = EPT Connect mapped drive Error Code = -1073573551 Error Detail = In Executing "C:\WINNT\system32\cmd.exe" "/C net use
\\servername\foldername /USER:userid password" at "", The process exit code was "1" while the expected was "0".

I have determined that a successfull connection should provide a exit code of 0.

The job runs under a proxy account but as explained when the package has run from within VS 2008 it was also tested to run under the proxy account and is successful.

It is not a 64-bit issue as I have tested it by running the package using the 32-bit version of dtexec.exe and the same problem occurs.

Also I have found that by running a simple command process within the Execute Process Task such as dir *.* it is successful when run from the job indicating that it is in fact something related to the net use command itself when run from

How to execute ssis package from stored procedure

how to excute ssis package from stored procedure and get the parameters back from ssis into the stored procedure.

SSIS Package execute error


1. I am trying to load data from AS400 DB2 to SQL Database using integration services.

2. I am using microsoft ole DB for Db2 driver to pull data from AS400 and using native SQL driver to load data into MS SQL 2005.


AS400 View to pull this data is---

                      INT(SVSGTP) AS AccountTypeID,  INT(SVTR) AS TranslationMethodID, INT(SVDEF)  AS AccountValue,  INT(SVRM)  AS RemeasurementID
FROM         V820PRMF.GSVL01


  AccountID String[DT_STR]   Lenhth-16

  AccountDesc String[DT_STR]  Length -30

  All other column is int.


MS SQL 2005 is were data   to be loaded. Table Info.


CREATE TABLE [dbo].[DimAccount](

[AccountID] [varchar](50) NOT

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

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