Join us for an expert-led overview of the tools and concepts you'll need to pass exam PL-300. The first session starts on June 11th. See you there!
Get registeredJoin us at FabCon Vienna from September 15-18, 2025, for the ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM. Get registered
Hi,
I'm making some experiments using the OPTIMIZE statement and VORDER configuration.
Basically, I create a table without the VORDER configuration and use OPTMIZE to apply the VORDER.
This should work according to this documentation: https://learn.microsoft.com/en-us/fabric/data-engineering/delta-optimization-and-v-order?tabs=sparks...
I few days (one week?) ago, I recorded a video executing these tasks and everything worked correctly.
Today I'm trying to execute these tasks again, while writing a blog post, and it's failing.
Was there any change in Fabric which caused this? Why the change is in conflict with the documentation?
Before:
The statement was accepted, it didn't caused any error:
Once executed, the VORDER appeared in the table metadata.
Now:
VORDER is pointed as an error by the intellisense:
It can be executed without errors, but the table metadata doesn't change.
Is this an issue, or is this a change of behaviour which is not in sync with the documentation yet ?
By the way:
I'm reading the metadata of the table, using the following code:
Kind Regards,
Dennes
Hi @DennesTorres ,
Thanks for using the Fabric community and reporting this .
I have reached to the internal for help on this. I will update you once I hear from them.
Hi @DennesTorres,
Thanks for reporting this and we can observe it as an issue. I have reached the internal Team regarding this. However, the Team is working on it and going to be fixed soon. I will inform if there is any update.
Thanks for understanding.
User | Count |
---|---|
13 | |
4 | |
3 | |
3 | |
3 |
User | Count |
---|---|
8 | |
8 | |
7 | |
6 | |
5 |