Two SSIS/BIDS/SQL oddities

[groleau]

Created an SSIS package in Visual Studio.

1. Last task is SQL. Output window always says "Sucess",
Fortunately the red box in the designer told me it
wasn't true. Scroll far enough to the right and there's
the error message. Unfortunately, it unhelpfully
listed several things that _might_ be wrong, none
of which actually were.

2. Project is under VSS source control. If the package
is checked in, attempt to Execute gets "Access Denied."
Checking it out and running it does not change the
package (VSS diff finds controlled copy and checked out
copy identical).

Responses welcome, but not needed---just venting.

--
Wes Groleau

http://www.Parkview.com/

 

[MDXer]

As for number 1 what I have noticed is that if you have you package set to allow a number of errors or your workflow is on complete and a task fails the package reports as completing successfully. I have had a couple packages like the above. I believe the reasoning is that since the Package completes it is seen as success where if the package and workflow is configured in such a way that the package fails on first error then it will report a failure.

This was a real pain when it is child packages that fail but the master reports success.

Paul
---------------------------------------
Shoot Me! Shoot Me NOW!!!
- Daffy Duck