You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There needs to be some better resilience in bulk insert process. I considered a "divide and conquer" approach that divides a failed batch statement into two halves and attempts the halves individually, recursively honing in on the failing individual row(s). I also noticed a single PK violation when adding dbo.DocumentField to AHreports in SqlChartify. This lead to some really weird behavior in SqlChartify desktop where it was continuing to run (with the error message box displayed), but resetting and updating the progress meter from scratch repeatedly. Wasn't sure what to make of that.
The text was updated successfully, but these errors were encountered:
There needs to be some better resilience in bulk insert process. I considered a "divide and conquer" approach that divides a failed batch statement into two halves and attempts the halves individually, recursively honing in on the failing individual row(s). I also noticed a single PK violation when adding dbo.DocumentField to AHreports in SqlChartify. This lead to some really weird behavior in SqlChartify desktop where it was continuing to run (with the error message box displayed), but resetting and updating the progress meter from scratch repeatedly. Wasn't sure what to make of that.
The text was updated successfully, but these errors were encountered: