Solved

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

Posted on 2008-06-20
4
216 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

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Question has a verified solution.

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

Real-time is more about the business, not the technology. In day-to-day life, to make real-time decisions like buying or investing, business needs the latest information(e.g. Gold Rate/Stock Rate). Unlike traditional days, you need not wait for a fe…
Recently we ran in to an issue while running some SQL jobs where we were trying to process the cubes.  We got an error saying failure stating 'NT SERVICE\SQLSERVERAGENT does not have access to Analysis Services. So this is a way to automate that wit…
This videos aims to give the viewer a basic demonstration of how a user can query current session information by using the SYS_CONTEXT function
Via a live example, show how to setup several different housekeeping processes for a SQL Server.

617 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