Catch SQL Action Error Text

  • Posts: 490
  • Karma: 2
  • Thank you received: 48

Catch SQL Action Error Text was created by bruce.gibbins

Hi.

I was wondering if there was a way to catch the Error Text from an SQL Action Item. Typically these actions go through without issue. However, sometimes we may make a slight environment change that breaks a package which we have not thought about or tested thoroughly enough. Then when we check through the child package logs we can easily see what we have forgotten to do. BUT... it would also save some time if the email alert we have could share the text of the underlying issue. This would then allow us to go straight to the source of the problem rather than reviewing the underlying logs.

This is also the case for a Transformation error. The execution log shows the detail of the error but if we could somehow have this bubbled up such that we can assign it to a execution variable then we can include it any email alerts we may send out.

For example, the screen shot shows an SQL Action object that failed as we had not created the underlying SQL stored procedure in the custom schema. Simple, to fix. But it would have been helpful if could catch this message text so that it could be included in the email that gets sent out on a failure. We DO send the package log. But because this is a sub-package, the parent log does not contain this detail. So we need to fire up AETL UI and then review the failed child log and take the appropriate action from there.

Thanks in advance if you see value in this.
cheers

11 months 1 week ago #21078
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 8458
  • Karma: 33
  • Thank you received: 567

Replied by admin on topic Catch SQL Action Error Text

Hello

As requested we added new variables you can use to the Transformation, SQL check, SQL Script, and Import objects.

Mike
ETL Architect
The following user(s) said Thank You: bruce.gibbins
11 months 1 week ago #21105
Attachments:

Please Log in or Create an account to join the conversation.

This site uses cookies. By continuing to browse the site, you are agreeing to our use of cookies