Fort Wayne, IN
|reply to drew |
Re: SQL Server Integration Services Maintenance Plan Package
I presume this is you or someone else working on the problem? If not, check out the reply there first.
SSIS is Greek to me, but just looking at the error message, I'm going to bet that RunID is returning null or an otherwise invalid GUID, which causes LEN to fail as well as the greater than 0 comparison. Or another possiblity, does RunID always return a guid and it may be an empty guid (all zeros) if it hasn't been initialized/set to a specific guid (similar to how guids are used in .NET)?
Port Orchard, WA
I've made some progress...
The RunId variable is not getting defined in the package created by BIDS. If I manually add it through BIDS, set the proper scope & namespace, we get a bit farther.
There seems to be a fundamental issue with the way a SSIS package is created versus the way a specialized IS package of type "Maintenance Plan" is created... there are other global variables that get added to the package by SQL Server/IS when trying to run the package after importing it.
I've got it working (after adding the variable), however the text-based reporting is completely broken. The "reporting tasks" (an item that can be defined within a package) are not getting created by the server and are unable to be defined at the package level within BIDS.
This issue is an artifact of the way we've chosen to do business - there's no need to template our maintenance plans if we weren't doing a separate plan for each DB.
flickr | 'Cause I've been waiting, all my life just waiting
For you to shine, shine your light on me