April 25, 2018 at 8:39 am
I have implemented a set-based try/catch with nested rbar fallback try/catch, as written up here by Mel Sansone: Conditional Set-Based Processing: Moving Towards a Best Practice for ETL
However, when I try to capture the data causing the error using FOR XML PATH (''), I get invalid XML, so I can't capture the data. My rbar approach flags each row with a success/failure, so I could identify the row causing the issue there, but it only seems to happen when loading as a set, not when loading each row.
Has anyone else run into this issue, and what did you do to identify what might be causing the problem, without logging through XML?
Thanks,
Jon
-------------------------------------------------------------------------------------------------------------------------------------
Please follow Best Practices For Posting On Forums to receive quicker and higher quality responses
April 25, 2018 at 9:23 am
So what error(s) are you getting when using FOR XML PATH('')?
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply