Prerequisites
You will be getting Windows or Linux version of Omni Loader, per your preference. In both versions, Omni Loader comes "with batteries included" and does not require additional framework installations.
There is no installation, you need to unpack the ZIP/TAR.GZ archive and can immediately run the application.
As data flows from source database to Omni Loader to target database/storage, the machine on which Omni Loader runs needs connectivity to the databases and storage accounts used.
When you run in a console mode, there are no additional requirements.
When you run in a standard standalone mode, browser is used for UI interactions with the user. Omni Loader comes with a built-in web server for that purpose, and by default listens on port 5000.
Here is an example for migration requirements from SQL Server to Fabric Warehouse.
Ensure you can connect to source database machine on port 1433, the default for SQL Server
Ensure you have read permissions for the source database on said server
Set up your Fabric account with appropriate capacity.
Ensure you can connect to Fabric Warehouse from that machine using Service Principal, the recommended way to access it. You can use SQL Server Management Studio for this purpose.
Set up ADLSv2 storage account and container for the staging data.
Ensure you have write permission to the ADLSv2 storage account container you will use as staging area. Omni Loader needs to be able to write to said container from this machine.
Ensure that Fabric Warehouse can read the same storage account container. You can upload a sample Parquet file and run a COPY INTO to ensure that ingestion works as expected.
Last updated