Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
subhash chandra
Starting Member
40 Posts |
Posted - 2009-01-28 : 04:31:11
|
Hi,I have a SSIS package that pulls data from oracle source. This package runs successfully when I run manually but were getting failed from SQL agent job. In a try I change the ProtectionLevel to ServerStorage. Now it is getting successfully complete but only within 4-5 seconds while it takes around 20 minutes when I run manually. I am not getting any history of SSIS package execution.Is there any configuration that I am missing in setting the job?If any one has faced this situation then please let me know how to find and resolve the problem.Thanks. |
|
RickD
Slow But Sure Yak Herding Master
3608 Posts |
Posted - 2009-01-28 : 06:25:15
|
Do you write to the file system anywhere in the package? Does SQL Server Agent service have sufficient rights to perform the task you have asked it to do?These are the two main questions I would ask. Until you have checked these, I would assume it was a permissions issue. |
 |
|
subhash chandra
Starting Member
40 Posts |
Posted - 2009-01-29 : 05:44:02
|
Thanks friends,I have found the solution. Actually in command line statement /Validate swith was added and because of it the package was just validating but bot executing. I just removed the switch and package run successfully. |
 |
|
TessZA
Starting Member
7 Posts |
Posted - 2009-01-30 : 07:59:52
|
Subhash, I have the same issue with one of my packages. The job in SQL Agent runs successfully (runs for 2hours as well), but does not actually execute the package & logs nothing in the logging table.Where do I check for this command line statement you are referring to? |
 |
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2009-01-30 : 12:55:10
|
in properties of sql agent job step. |
 |
|
|
|
|