Forum Discussion
SQL Analytics Endpoint - Table constraints disappear after running Dataflow Gen2
- 2 years ago
Oh, I see... My bad. It's not regular Replace I am using. I am actually using Replace with Dynamic schema. I had forgotten that. (I now changed the info to Replace with Dynamic schema also in my previous comments)
I guess the Dynamic schema setting is causing the table to get dropped and recreated.
I still find it inconsistent that the constraints and model relationships are affected differently by this operation.However, for my use, the model relationships are more important than the table constraints. So I like that the model relationships are not being dropped at least.
I just need to beware not to use the expand column option in Power Query for my import mode semantic models, when working with lakehouse tables which are subject to Dynamic schema.
As the expand column option seems to be depending on the table constraints in the SQL Analytics Endpoint, and the table constraints don't seem to get recreated when the table gets dropped and recreated.I would prefer that the table constraints also keep working after running a Dataflow Gen2 with Dynamic schema, similar like the model relationships.
I am suspecting that the reason is that the Dataflow Gen2 drops and recreates the Lakehouse table when using Replace mode with Dynamic schema.
So maybe that's why the constraints are removed (or rather: not re-applied) from the tables in the SQL Analytics Endpoint?
However, I think it's not consistent with the model relationships still being present and working afterwards.
These are the destination settings in my Dataflow Gen2: