.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

Debugging SSIS packages

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

When I attempt to run an SSIS package interactively in Visual Studio 2005, I am getting a different SSIS package from the same project opening in debug mode instead?

I had a similar issue on my old PC but as It was being replaced, I didn't worry too much but I now have the issue again.  Please tell me there is someone else out there experiencing the same frustrating issue?

If I import the package I want to run to a new project then I can run it interactively but this is a pain of a work around.


View Complete Post

More Related Resource Links

Transactions in SSIS packages

Hi guys - I've been working in ssis for a bit but never have encountered the need for transactions - until I realized that I really need them. Here's my setup. I have a master package that has a sequence container in it. In that sequence container are 3 execute package tasks (Insert - Update - Delete). Each execute package task points to a child package which contains 50 execute package tasks (to perform the tasks on my different tables). From there - the actual work is done. (default everything on transaction/isolation etc) My problem/question is that I need to make it where if the insert fails, the update/delete do not happen and everything gets rolled back. Right now if something fails it just stops there and gives me half changed records. Is there a way to do this or am I just hoping for un-doable? Thanks!

Issues with running SSIS packages programmatically

Hi, I have spent days trying to solve this problem and still stuck with this and I have posted some questions already in forums, but didn't get satisfactory answers. I am trying to be more clear this time and hope to get a better answer. I have gone through this article already http://blogs.msdn.com/b/michen/archive/2007/03/22/running-ssis-package-programmatically.aspx and here are my issues (I need to run the SSIS package from ASP.NET) option 1 is not suitable for me, because it may recycle worker process if it consumes memory option 2 is also not suitable because of security issues in creating a new process and passing the context to new process looks very complicated for me (according to the support article) option 3 is not suitable because using SQL Server Agent to run SSIS package is not allowed by the company I am working for(I guesss it requires installation of db engine on application server, not sure). but SSIS is installed on the application server. option 4&5 will have the same issues as options 1&2. I guess the only option left now is to create a windows service and start the service from ASP.NET. but will this allow running multiple packages in parallel? OR is there a better alternate solution for this? please let me know. Thanks.

How to merge SSIS packages

Hi Guys, Is there any way to merge changes into SSIS package under version control. It's a plain XML, which is easy to merge, but it's also quite easy to make the package invalid. Would appreciate any ideas. Thanks, V.

How to deploy and configure ssis packages using sql server table in testing server and production en

Hi We have three environments (development, testing and production ) I have to configure and deploy the ssis packages using sqlserver table in different environments(development, testing and production).   Three environments database structures  are same But database names are different like (DEVSERVER,SITSERVER,UATSERVER) We have 14 packages and one master package. In master package we called all 14 packages question1 First time i will deploy all (master and 14 packages). If i modify one package we need to deploy all the packages or single package deployment is enough    Please help me thanks in advance          

How to remove deployed SSIS packages to SQL Server 2005?

Hi All I need to find a way of removing all packages deployed to a SQL server - can this be done?   Thanks   Big Gopher

OS upgrades & risk on mission critical SSIS packages?

Hi Folks A risk management question. We are considering upgrading from Window Server 2003 to Windows Server 2008 R2. We currently have SQL 2008 sitting on top of of WS 2003 and  have a number of mission critical SSIS packages that run on the machine.   Do OS upgrades pose much risk to SSIS packages? Any suggestions or thoughts would be appreciated.    Thanks  Steve     

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.

Copy SSIS packages from 2005 to 2008

I have both vs 2005 and vs2008 on the same pc. When i try to copy the package from the BIDS 2008 from file Copy as i get an error

 Storing or modifying packages in SQL Server requires the SSIS runtime and database to be the same version. Storing packages in earlier versions is not supported.

Do you know how to fix this issue.

Debugging (Large) Legacy SSIS Projects



I've been given the enviable task of updating someone else's SSIS project that has been running in production for some time. There was no development server at the time it was created and no project files available so I have had to copy the dtsx files plus any other supporting files onto my dev server.

I've battled for a few days with connection managers not wanting to update (literally change data source, save, close, open and the datasource reverted back to what it was!), interesting configurations and various other odd things.

Currently, I have two more general SSIS questions

1) When I run my current job, it gets about 30% of the way through in about 3 minutes. It then seems to wait for about another 3 minutes, apparently doing nothing, then continues before failing (see 2). Is there any way I can trace why it is pausing or what it is doing at that time? The processor/ram seem quiet and SQL profiler doesn't tell me a lot is happening. I couldn't think of anything else. My next step would be to add some more logging but not sure where to put it!

2) My job eventually fails at a parent package (LoadDim.dtsx) which I have cut down to execute only 3 of the the child packages DIM1.dtsx, DIM2.dtsx & DIM3.dtsx. The parent Progress tab reports that DIM1.dtsx has failed so I open DIM1 and all is steps are green and there are no err

How many type of loops are there in SSIS Packages?

How many type of loops are there in SSIS Packages?

SSIS Packages Job Fails



When i am trying to execute the SSIS Package in BIDS, it works fine. When I schedule the same package as job in SQL Server Agent it gives the following error.

Here is the complete log information:

Log  Job History (ssis)

Step ID  1
Server  DTC270031600465
Job Name  ssis
Step Name  ssis
Duration  00:00:00
Sql Severity  0
Sql Message ID  0
Operator Emailed  
Operator Net sent  
Operator Paged  
Retries Attempted  0

Executed as user: NT AUTHORITY\NETWORK SERVICE. The package could not be found.  The step failed.

i tried to run the job with proxy accounts also but it didnt work for me. Please help me.

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?


Security for SSIS packages

What are the security levels present in SSIS for a package?

SSIS on Cluster also 2005 packages and 2008 db connections and jobs?


Hi, multipart questions.

We have a SQL 2008 Cluster where we do not want to install SSIS.  We have a SQL 2005 SSIS instance on another server  for packages.

here goes

1. Can we configure jobs on the SQL 2008 custer to point to the 2005 SSIS instance? and do we need SSIS installed on the SQL 2008 cluster to do this?

2. Can we run jobs on a SQL 2005 instance, pointing to a SQL 2005 SSIS instance/packages on a third server that connect to a SQL 2008 DB instance . I know that sounds crazy, but where exactly is the CPU and memory load in that design.. job on one server, package a seperate server and db on a third server.?

3. As mentioned, I have SQL 2005 SSIS instance.  I have local admin on that server and can connect to the ssis instance from my sql 2005 sql client on my desktop.  I added a new user to the server and added them to the SSIS and users group. I also made sure they could write to the folder where they will deploy packages. However, they get some kind of access denied while trying to connect, unless I give them local admin on the server.  What more access do they need than to be in the users and SSIS group and have write access to an SSIS deployment folders?


Many Thanks.

MS SQL 2005 SP2 x64 & SSIS Packages


On my local desktop, I can create and run ssis packages, when I try to do the same thing on server I get he following error right clicking on running packages or stored packages.


failed to retrieve data for this request. Library not Registered. (exception from HRESULT: 0x8002801D


there are 2 instances of SQL on this server. Both are named with one being use by SQLExpress and the other by SQL2005 Std


Visual Studio 2008 and SQL Server 2005 SSIS packages


My home machine has sql 2005  and Visual Studio 2005 installed. I uninstalled VS 2005 (RTM) and installed VS 2008 (RTM) in its place. I then found that the SSIS templates were missing. Lesson: don't uninstall VS 2005 if you want to use SSIS 2005!


1. Is there any "workaround" to this issue?


2. (If the answer to 1 is "No") I will install VS 2008 side-by-side with VS 2005 on the same box.  When the SSIS issue is finally resolved, can I uninstall VS 2005 without doing damage to the VS 2008 install?










SSIS packages writen with ssis2005 run under 2008

Will SSIS packages writen with ssis2005 run used 2008 dtexec.exe?  General situation. DB will be upgrade from sql 2005 to sql2008 on a new box. Will the application packages need to be upgraded or will the sql2008 dtexec.exe run them as is?
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