Viewing 7 posts - 1 through 7 (of 7 total)
correct...my mistake, i haven't read the line carefully!
February 22, 2011 at 11:30 pm
to fail the container on a failure, the best option is failparentonfaliure=true... i agree...
i was thinking about catching the error and continuing the flow. 😉
February 17, 2011 at 10:52 pm
Are you looking for a native tool...
if so you can use compress
for that u need to ask ur admin to install this toolkit for u.
February 14, 2011 at 11:21 pm
Well,
one option is like....you can add some logging task inside the container and connect that task with all possible error outputs from the different tasks inside the container.
and in the...
February 14, 2011 at 11:09 pm
In most of the cases,
When you deploy and schedule a Package using SQL Agent Job, the package should be on the agent account,
And normally its should be NTAuthority/NetworkService
Please check that...
February 14, 2011 at 10:58 pm
The best option should be 7zip which is an open source licence
we have a 7-Zip Command Line Version available for download(http://www.7-zip.org/download.html)
use that one with commands as Expressions along...
February 11, 2011 at 11:44 pm
This might be due to access restrictions,
in debug its running on your windows account,
but after deployment it should be on Service or SQL Agent account...
So if your package accessing restricted...
February 11, 2011 at 11:35 pm
Viewing 7 posts - 1 through 7 (of 7 total)