Difference between SSIS Packages manually launched and Scheduled

Question

Difference between SSIS Packages manually launched and Scheduled

guennal

SSC Enthusiast

Points: 161
More actions
March 8, 2010 at 2:36 pm

#386460

Hello
I have some difficulties to retrieve data from AS 400 Tables to my SQL Server 2005 database (I use SQL Server 2005 Enterprise Edition on a Microsoft Server 2003 X64 Edtion)
I try to solve my problem but unsuccessfully for the moment
Here it is :
I got a SSIS package where I load data in a simple SQL Server table
I use 2 ways to execute it
1) I schedule a SSIS package through a Job
=> I get 135 Rows in this daily scheduled job
2) I launch the same job manually OR I execute the package through BIDS
=> I get 140 Lines (so 5 lines in difference)
I check which is the correct value
and this is always the manually launched one
I get the same error for several tables(scheduled jobs give always less data than in the other case.
SQL server 2005 give me no error message.
Any ideas ?
Thanks in advance
David

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

TangoVictor SSChampion Points: 10976 More actions · Answer 1

do you get any error messages?

One thing I ran across is an OLE DB connection to DB2 returning incorrect row counts. I use all ODBC connections for DB2 and use a script component as a source, I use the script component so I can dynamically build the select statement.

guennal SSC Enthusiast Points: 161 More actions · Answer 2

Hello Tom,

Thank you for your reply

I get no error message from SQL Server

Jobs and Packages run always successfully (even when data are missing)

I use ODBC Connection and it's always the same AS 400 User/password used.

(I checked this point in package configuration also)

TangoVictor SSChampion Points: 10976 More actions · Answer 3

The only other thing I can think of and this really only applies if you have some type of dynamic parameter that could filtering the data and the expression or data used for that dynamic parameter is not being set correctly when scheduled due to a permission issue.

99% of issues I run into between running interactive and scheduled is a permission problem.

One thing you could try is to setup a proxy account using your credentials and have the job run under that proxy. That way you are essentially executing the job as yourself, any permission you have the job will have. This is aside from the 400 connection which I know is the same regardless of how the job is run.

Lastly is there possibly a copy of the table in another library that it could be accessing - long shot I know, grasping a bit here.

Tom