July 8, 2015 at 12:05 am
Comments posted to this topic are about the item Extending Custom Execution in the SSIS Catalog – Level 21 of the Stairway to Integration Services
Andy Leonard, Chief Data Engineer, Enterprise Data & Analytics
November 9, 2015 at 2:08 pm
Hi Andy,
Thanks a lot for one more great article.
One typo that I found here is:
"For the second test, let’s execute custom.execute_catalog_package, setting the new @synchronized parameter to 0 as shown in Listing 5:"
Actually, for the second test, the @synchronized parameter is set to 1.
IMHO, having some typos is not necessarily bad: it keeps the readers on their toes 🙂
March 10, 2016 at 9:13 am
Hi Andy
Thanks for the article – I think I missed it the first time round.
I wonder whether you have any intention of talking about how to set up scripted deployments of environments, environment references and project configurations (to assign environment variables to project and package parameters)?
Someone, somewhere must have set this up as part of their CI processes.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply