Are schema updates quicker to reflect in sql endpoint & semantic models with a more powerful sku?

[wilson_smyth]

We are trying out fabric with F2 & F4 skus.
We are finding that the time for schema changes to be reflected in the sql endpoint are significant.
If we add a table to a view, add or delete a view in the sql endpoint, its not visible in the tables section to the left for at least 30 minutes.
It is often not available to the default schema for hours.
When it finally appears, we get an error creating relationships for a further few mins.

This is massively slowing down progress as it disrupts the development/engineering workflow.

Is this just how fabric is right now, or is performance better in the higher tier skus like F64?

[Anonymous]

Hi @wilson_smyth,

In fact, this delay already mentioned in official documents. The sync operation not only sync the table but also include many other processions.(for example: sync table from Lakehouse to warehouse, detect and binding data type and relationship column mapping, registrations correspond contents and artifact in capacity, etc..)

Regards,

Xiaoxin Sheng

[lbendlin]

Same across all SKUs as far as we can tell.