Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 

James Serra's Blog

James is currently a Senior Business Intelligence Architect/Developer and has over 20 years of IT experience. James started his career as a software developer, then became a DBA 12 years ago, and for the last five years he has been working extensively with Business Intelligence using the SQL Server BI stack (SSAS, SSRS, and SSIS). James has been at times a permanent employee, consultant, contractor, and owner of his own business. All these experiences along with continuous learning has helped James to develop many successful data warehouse and BI projects. James has earned the MCITP Business Developer 2008, MCITP Database Administrator 2008, and MCITP Database Developer 2008, and has a Bachelor of Science degree in Computer Engineering. His blog is at .

SSIS package runs fine until put in a job

I see this issue pop up every now and then: A developer creates an SSIS package in BIDS and gets it to run fine.  Then the developer connects to Integration Services and uploads the package to the server, and then uses the Run Package, and again it runs fine.  But once the developer creates a job that runs the package, the job fails, despite all the correct security settings.

It’s a bit confusing: when you use the “Run Package” command in SSMS when connected to Integration Services, it starts the Execute Package utility (dtexecui.exe), which always runs a package on the local computer, even if the package is saved on a remote server.

So, if the package is using a local resource that is not there by default, like an Oracle ODBC driver, you must install that driver on the server that the package is on in order to get things working.

Comments

No comments.

Leave a Comment

Please register or log in to leave a comment.