Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

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

Posted on 2008-06-20
4
Medium Priority
?
217 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 400 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 100 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

Congratulations! You’re Certified – Now What?

Starting a new career can be overwhelming. Becoming certified in your field of expertise is a great start, but where do you go from here?  Here are some tips to help you on your career journey.

Question has a verified solution.

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

Ever wondered why sometimes your SQL Server is slow or unresponsive with connections spiking up but by the time you go in, all is well? The following article will show you how to install and configure a SQL job that will send you email alerts includ…
This article shows how to deploy dynamic backgrounds to computers depending on the aspect ratio of display
Viewers will learn how to use the INSERT statement to insert data into their tables. It will also introduce the NULL statement, to show them what happens when no value is giving for any given column.
Viewers will learn how to use the SELECT statement in SQL to return specific rows and columns, with various degrees of sorting and limits in place.

721 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