April 10, 2013 at 2:19 am
Hi,
I have a SSIS package that picks up csv files from a shared folder on daily basis and load the data into sql database.
When I execute the package in Bids environment everythin works fine. But, when I try setting up an schedule for the package, then the job fails.
I assume my SQL account doesnt have permissions to access the folder. how am I suppose to ensure that the sql account has required permissions to access the folder?
Thanks!
April 10, 2013 at 7:34 am
Are you using the SQL Agent to schedule the package? What error does it return?
April 11, 2013 at 7:33 am
Getting a package to work as well as a job as it does in BIDS is one of the most common and frustrating challenges SSIS developers experience. Often, a job (which calls a package) will just hang and there is limited information given in the job's history log.
What I have found is atomizing everything helps. Split up every individual operation into its own script task and make sure your log table (if you have one) indicates where you are before the job hangs.
Good luck--the SQL Agent has sure taken me down some difficult roads.
April 12, 2013 at 1:33 pm
This KB article covers a lot of the most common reasons for the problem you are describing. I pass it along quite often:
SSIS package does not run when called from a SQL Server Agent job step
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply