New

Use Fabric Warehouse for Prepare instance storage (Public Preview)

This article describes how to set up Prepare instances with Fabric Warehouse storage.

Fabric Warehouse Prepare instance storage is available as part of the Standard, Premium or Enterprise Package

A public preview of this feature is currently available at simple mode level. In addition to that, the following limitations apply:

You can only copy data from Ingest instances using Fabric Lakehouse storage and the Ingest and Prepare storages must be in the same Fabric Workspace.

Prerequisites

Your Ingest instance must use Fabric Lakehouse storage and be located in the same Fabric workspace as the Warehouse.
Create an App Registration in the Azure Portal. It is recommended to use a dedicated app registration to ensure this account is the only one with access to the client credentials.
In the Fabric/Power BI Admin Portal, enable the following settings and ensure they are enabled for the app registration if using specific security groups:
- Users can create Fabric items
- Service principals can create workspaces, connections and deployment pipelines
- Service principals can call Fabric public APIs
In the Fabric portal, navigate to your workspace and select Manage access. Grant the App Registration account Member access to the workspace.
Create a Fabric Warehouse in the workspace, or use an existing one.

Add a Prepare instance and select the storage type Microsoft Fabric Warehouse.
Enter the workspace name for the existing Fabric workspace.
Enter the name of the Fabric Warehouse.
Enter the Tenant ID for the tenant associated with Fabric.
Enter the Application ID for the App Registration.
Enter the Application Key (i.e. the client secret value) associated with the App Registration.
Open TimeXtender Data Integration and open the instance you just created.
If you are not using an existing Warehouse, right click the instance, click Edit… and then click Create Storage…
Right click the instance and click Advanced > Create Required Objects for Fabric Warehouse. Unlike other SQL storage types, Fabric Warehouse does not support standard SQL extended properties. TimeXtender therefore creates dedicated tracking tables in the ‘dbo’ schema within the Warehouse to manage table metadata and enable differential deployment.

Once the required objects are in place, you can deploy and execute tables in the same way as with other storage types.

For tables with incremental load enabled: both an incremental table and a raw table are created in the Warehouse.
For regular (non-incremental) tables: only the valid table is created.

Note: Tables are not created in the Fabric Warehouse until you execute the table. Empty tables are not created.