Omni Loader Docs
  • OVERVIEW
    • About
    • Getting Started
    • Databases
    • Performance considerations
    • Prerequisites
  • Project Wizard
    • General
    • Database List
    • Favorites
    • Review
  • Project types
    • Full Table Copy
    • Data Compare & Sync
    • Change Data Capture
    • Overview
  • Project Options
    • General
    • Performance
    • Databases
    • Mapping
    • Logging
    • Troubleshooting
  • Table Options
    • Columns
    • WHERE clause
    • Partitioning
    • Cut-off
    • Options Override
  • Global Settings
    • Overview
  • Automations
    • Overview
    • JSON job specification
  • Connections
    • Amazon RedShift
    • Analytics Platform System
    • Synapse Dedicated Pool
    • CockroachDB
    • CSV
    • Databricks
    • DB2 iSeries
    • DB2 LUW
    • DB2 zOS
    • Greenplum
    • Google AlloyDB
    • Google BigQuery
    • MariaDB
    • MySQL
    • Netezza
    • NuoDB
    • ODBC
    • Oracle
    • Parquet
    • PostgreSQL
    • Snowflake
    • Sybase ASE
    • Sybase IQ
    • SQL Server
    • Teradata
    • Vertica ODBC
    • Fabric Lakehouse
    • Fabric Warehouse
    • Azure SQL Database
    • V-ORDER Fabric Lakehouse Optimization
Powered by GitBook
On this page
  • For Target Only
  • Omni Loader connection to storage
  • Complete steps to enable V-ORDER optimization
  1. Connections

Fabric Lakehouse

PreviousVertica ODBCNextFabric Warehouse

Last updated 10 months ago

Connecting to Microsoft Fabric Lakehouse is a seamless process, similar to connecting to familiar SQL environments.

Server is the SQL Analytics endpoint as exposed by the Fabric. To find out the correct URL, please open your lakehouse, click the Settings gear icon in the top-left corner, then navigate to the SQL analytics endpoint section and copy the link.

Database name - click on Select to pick a database from the list of all databases available on the server, or type in by hand.

For Target Only

Data is loaded into the lakehouse by uploading data files (Parquet) and triggering the ingestion by the lakehouse. This means that both Omni Loader and Fabric Lakehouse need access to the storage. As Omni Loader can run both on premises and the cloud, while Fabric Lakehouse is cloud-only, you might have to configure their access differently.

Omni Loader connection to storage

  • Workspace Type in the name of your Fabric workspace

  • Run V-ORDER optimization After loading the data, use the compute of your Fabric tenant to post-process your Parquet data files and maximize the performance

Complete steps to enable V-ORDER optimization