Proactive Transform Binding Error Reports

Many of us carry some scripts in our pocket from Project to Project. I use a stored procedure to proactively identify views with binding errors.

The attached ZIP file contains scripts to create the Stored Procedure, Views, and Table required to identify views (Specifically views registered in Transform) with binding errors in a specific database. Also attached is a Sample Snapshot of the Stored Procedure results. 

You can save yourself heartache by running the BindingError_Reports stored procedure in your dswXXX database then making the necessary corrections. The alternative is do nothing until the Transform job fails then fix the error after the job fails…each time a Binding Error is encountered.

I'm not sure of the best location for these reports but one idea is to include them in the TRANSFORM REPORTS Page.

Binding Error S...
Binding Error R...
Attachments Open full size
  • Tracey Karanovich
  • Nov 15 2017
  • Already exists
Advanced Data Migration (SST) / Transform
  • Nov 15, 2017

    Admin response

    On the vertical view of any datasource you can recompile the database and see what objects will fail to run.

  • Attach files
  • Tracey Karanovich commented
    22 Nov, 2017 04:02am

    The existing ability to recompile a database is not a substitute for the functionality illustrated in the Binding Error Report Example I attached. 

    1. We would never opt to recompile the database to find binding errors because it updates the MODIFIED DATE for every view in the database. The view's MODIFIED DATE is important when sorting the views to find specific views or determining when a change was introduced. Developers would go nuts if someone re-compiled their dswXXXX database causing all the views to be set with the current date.
    2. The error message displayed in DSP is not practical to use. Someone trying to fix all the binding errors would need to take screenshots of the error message and you can't copy a view name from a screenshot.
    3. Not all the errors displayed as a result of re-compiling the Database are critical. While in theory, they should all be fixed. During the time crunch imposed by a project, we don't have that luxury. We need to fix those that involve registered views. In particular those that are actually active. As shown in the attached example, There are separate reports for Source Rules, Source Reports, Target Rules, and Target Reports in addition to an overall list of views with binding errors.
    Attachments Open full size

Related ideas