Hi,
I am trying to merge data into a table in a Fabric warehouse.
Since MERGE is not supported yet, I am performing the merge in two steps: Update exising entries and Insert new entries (for this specific table, no delete is required).
We'll only have look at the update part, since this already causes the error by itself:
When i run this (simplified version) as a regular SQL-Statement, it works:
UPDATE DWH.Customer
SET Name= SRC.Name
FROM DWH.Customer DST
INNER JOIN Stage.Customer SRC
ON DST.Company = SRC.Company
AND DST.Code = SRC.Code;
This completes in about 5 seconds.
When I wrap the whole thing in a stored procedure, it runs for a while and then fails with:
"Maximum stored procedure, function, trigger, or view nesting level exceeded (limit 32)."
Interstingly, the update works correctly, but the process keeps running for an additional 10 seconds before it fails.
Any ideas what causes this and how to fix it? I ran into something similar years ago in a customer project where they were using an ungodly logic based on hundereds of triggers. Then, the error made sense. But joining two tables should not cause this.
UPDATE:
I have an update on this. I tried the same approach for a different table (which has more columns and rows and addtional field on which I perform the join) and it works. Does this have something to do with the underlying delta structure (e.g. Fabric performing additional joins under the hood, over which I have little control)?
