Solved

Issue with SSIS packages not completing when run via a SQL job

Posted on 2008-06-20
4
215 Views
Last Modified: 2013-11-26
I have created a number of SSIS packages that run fantastically through Visual Studio.  However, when I add a number of these packages into one sequential SQL job, the job never completes.  It does not error but just remains in an "executing" state when looking at the job activity monitor.  I have no clue why they would run fine when executed in VS but never complete when executed in SQL.  Not all jobs fail in SQL.  I have other jobs which contain SSIS packages which run fine in SQL so I think the configuration is alright.  I need to supply more information but don't know where to start so any assistance or request for more detail will be greatly appreciated.
0
Comment
Question by:m12white
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
4 Comments
 
LVL 31

Assisted Solution

by:James Murrell
James Murrell earned 100 total points
ID: 21836692
could it be a permissions?
0
 

Author Comment

by:m12white
ID: 21838055
Unsure.  I've tried the SQL Agent under the administrators account.  No change.  It almost looks like a scheduling problem but these jobs were setup identically to a much smaller server running sql 2000 that ran this consolidated schedule just fine (albeit slowly).  This server is a new and very powerful unit that I wouldn't expect to have problems with jobs running simultaneously.
0
 
LVL 30

Assisted Solution

by:nmcdermaid
nmcdermaid earned 25 total points
ID: 21843358
>> need to supply more information

Turn on logging for the package(s) and see where its getting stuck.

If I recall correctly, you need to specifically create a logging connection manager and use that.
0
 

Accepted Solution

by:
m12white earned 0 total points
ID: 21843364
I think I've found it.  Sorry...but thanks for the help.  Apparently, my use of a query multiple times was causing the issue.  I'm new to SSIS so I finallly figured out that I needed, and could, multicast that dataset to the areas needed.  This appears to have cleared up my stalling jobs. I'm still not sure if this was a locking problem or other but it appears to be working.
0

Featured Post

The Eight Noble Truths of Backup and Recovery

How can IT departments tackle the challenges of a Big Data world? This white paper provides a roadmap to success and helps companies ensure that all their data is safe and secure, no matter if it resides on-premise with physical or virtual machines or in the cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In this article we will get to know that how can we recover deleted data if it happens accidently. We really can recover deleted rows if we know the time when data is deleted by using the transaction log.
JSON is being used more and more, besides XML, and you surely wanted to parse the data out into SQL instead of doing it in some Javascript. The below function in SQL Server can do the job for you, returning a quick table with the parsed data.
This video shows how to set up a shell script to accept a positional parameter when called, pass that to a SQL script, accept the output from the statement back and then manipulate it in the Shell.
Via a live example combined with referencing Books Online, show some of the information that can be extracted from the Catalog Views in SQL Server.

734 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question