Events
Mar 31, 11 PM - Apr 2, 11 PM
The biggest Fabric, Power BI, and SQL learning event. March 31 – April 2. Use code FABINSIDER to save $400.
Register todayThis browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Applies to: ✅ Warehouse in Microsoft Fabric
The Warehouse in Microsoft Fabric storage uses the Delta Lake table format for all user data. In addition to optimizations provided by the Delta format, a warehouse applies optimizations to storage to provide faster query performance on analytics scenarios while maintaining adherence to the Parquet format. This article covers V-Order write optimization, its benefits, and how to control it.
V-Order is a write time optimization to the parquet file format that enables lightning-fast reads under the Microsoft Fabric compute engines, such as Power BI, SQL, Spark, and others.
Power BI and SQL engines make use of Microsoft Verti-Scan technology and V-Ordered parquet files to achieve in-memory-like data access times. Spark and other non-Verti-Scan compute engines also benefit from the V-Ordered files with an average of 10% faster read times, with some scenarios up to 50%.
V-Order works by applying special sorting, row group distribution, dictionary encoding, and compression on Parquet files. As a result, compute engines require less network, disk, and CPU resources to read data from storage, providing cost efficiency and performance. It's 100% compliant to the open-source parquet format; all parquet engines can read it as regular parquet files.
Consider the following before deciding to disable V-Order:
Consider the effect of V-Order on performance before deciding if disabling V-Order is right for you.
Caution
Currently, disabling V-Order can only be done at the warehouse level, and it is irreversible: once disabled, it cannot be enabled again. Users must consider the performance if they choose to Disable V-Order in Fabric Warehouse.
Disabling V-Order can be useful for write-intensive warehouses, such as for warehouses that are dedicated to staging data as part of a data ingestion process. Staging tables are often dropped and recreated (or truncated) to process new data. These staging tables might then be read only once or twice, which might not justify the ingestion time added by applying V-Order. By disabling V-Order and reducing the time to ingest data, your overall time to process data during ingestion jobs might be reduced. In this case, you should segment the staging warehouse from your main user-facing warehouse, so that the analytics queries and Power BI can benefit from V-Order.
Events
Mar 31, 11 PM - Apr 2, 11 PM
The biggest Fabric, Power BI, and SQL learning event. March 31 – April 2. Use code FABINSIDER to save $400.
Register todayTraining
Module
Get started with data warehouses in Microsoft Fabric - Training
Understand the key components and design considerations for implementation of data warehouses in Microsoft Fabric.
Certification
Microsoft Certified: Fabric Data Engineer Associate - Certifications
As a Fabric Data Engineer, you should have subject matter expertise with data loading patterns, data architectures, and orchestration processes.