If you’ve been doing any development work in ADF this week you might have noticed that “Connections” has moved. But where has it gone?
When you click onto “Connections” now you’ll receive the following message:
Clicking this button takes you to the new Management Hub, the new fourth icon which goes alongside the existing three.
Within this area you now have access to your Linked Services, Integration Runtimes and Triggers. These all have the same options as before, they’ve just moved!
You do now have access to more detailed Git configuration options and also the ability to change the Parameterization templates for your ARM templates. This is only accessible when you have a Git repository set up and the Parameter file within it.
You can currently still access Triggers from the main Author window, but I would recommend getting used to finding them in the Management Hub to keep everything together.
Release details of the Management Hub from Microsoft can be found here: https://docs.microsoft.com/en-us/azure/data-factory/author-management-hub
Azure Data Factory (ADF) Parent Activities don’t trigger ON ERROR OUTPUT when Child Activities Error… What happens?
So that title is a big question that a client of ours came across that required some additional investigation… What does happen and how do we get around it?
In the below example we’ll use a simple IF Activity as our Parent Activity. To explain briefly how it functions, you provide it with a query that evaluates to either True of False. This then passes down to a set of Activities If True and a different set of Activities If False. We then have three Outputs, On Success, On Failure and On Completion. This looks like:
The IF Activity therefore has logically four different things it does given the query criteria:
- If the query evaluates correctly, then:
- If True, Pass to True Activities
- If False, Pass to False Activities
- Error Activity if the query doesn’t evaluate to True or False.
Following that, we have the below options:
- When 1. If True Activities complete with Success, Trigger On Success Output and On Completion Output
- When 1. If False Activities complete with Success, Trigger On Success Output and On Completion Output
- When 2. completes with Error, Trigger On Error Output and On Completion Output
The issue occurs with the below options:
What happens when the If True Activities complete with Error?
What happens when the If False Activities complete with Error?
Logically you would expect that to cause the IF Activity to error as well. Right? WRONG!
Although it shows as if it has an error in the pipeline view:
The details show “Activity failed because an inner activity failed.”:
This means that the IF Activity itself has still started down it’s success pathway and is now just showing the error from further down. This causes the IF Activity to complete with neither Success or Error! (You can see this in Image 2 above). You can also see that the On Completion Output has triggered successfully.
This means that the Error Output of the If Activity can only be used to handle Errors on the Evaluation of the If Query itself. (When it can’t get to true or false, or can’t execute for another reason).
If you want to monitor the steps inside the IF Activity, you’ll need to put those output pathways inside the True and/or False activities themselves and handle this at a deeper level.
I have launched a new twitter account http://www.twitter.com/PurpleFrogReiss so please follow me there for updates on when I post new blog posts!
If you’ve tried deploying a .ispac using the Integration Services Deployment Wizard, you may have come across the following error:
By default SQL Server uses the 32-bit version of the Deployment Wizard, which is why you’ll be getting the Out of Memory error. If you instead launch the Wizard from the 64-bit location, (default is C:\Program Files\Microsoft SQL Server\130\DTS\Binn\ISDeploymentWizard.exe), then you should be able to deploy with no problem. (Please note, the “130” part of the above string may be different, depending on the version of SQL you have installed. This may reside in one of the other numbered folders in that location).
Using the same server and same project, the 32-bit deployment took over an hour and then failed with the error message, while the 64-bit took under a minute and deployed without issue!