Skip to content
KNIME Documentation
Main Navigation Get startedBuildWork with KnimeAccount and adminRelease notesDeveloper tools
Community Hub
DevelopersKnime
Sidebar Navigation

Getting Started

Installation

User Guide

Release Notes

Install Extensions

Building Workflows

Components

Flow Control

Expressions

File Handling

Deployment

Integrated Deployment

Workflow Invocation

Best Practices

Advanced Features

AI Extension

Get Started

Build an Agent

Inject context with RAG

LLM Providers

Tutorials

Summarize product reviews

Product FAQ assistant

Restaurant agent

Your first local agent

Task extractor

Reporting

Kerberos

Extensions

Database

Overview

Tutorials

Read and filter data from a database

Write a transformed dataset to a database

Concepts

Ports and Sessions

Query Generation

Type Mapping

Deprecated Framework

Connecting

Connect: Dedicated Node

Connect: File-Based Database

Connect: Generic DB Connector

Register a JDBC Driver

Install Third-Party Driver Plug-in

Drivers on Hub and Server

Kerberos Constrained Delegation

Reading and Transforming

Read Data

Transform Data Visually

Run a Custom SQL Query

Parameterize a Query

Writing and Modifying

Insert, Update, or Merge

Delete Rows

Bulk Load Data

Create and Remove Tables

Use Transactions

Reference

Connector Node Settings

JDBC Driver Reference

Deprecated Node Mapping

Migrate Deprecated Workflows

Python

Overview

Tutorials

Python Scripting Quickstart

Data App Development Using Plotly

Data Processing

K-AI Scripting Assistant

Data Type Conversion

Batch Processing

Jupyter Integration

Environment Management

Pixi Configuration

Dependency Management

Environment Persistence

Channel Mirrors & Air-Gapped Setups

Conda Migration

Alternative Configurations

Conda and Miniforge Setup

Conda Environment Propagation

Manual Python Configuration

Legacy Node Migration

Concepts

Pixi Backend Architecture

Storage Logic

Python Environments on Executors

Reference

Python Scripting API

Bundled Packages

Executor and Hub Configuration

Troubleshooting Guide

API Reference

Inputs and outputs

Classes

Views

Utility functions

R

Deep Learning

Snowflake

Google Cloud

Azure

AWS

Big Data

Big Data Admin

Big Data Secured Cluster

Databricks

Microsoft Fabric

Power BI

Tableau

Report Designer

H2O

Changelogs

Version 5.12

Version 5.11

Version 5.10

Version 5.9

Version 5.8

Version 5.7

Version 5.6

Version 5.5

Version 5.3

Extensions

Work with Microsoft Fabric Data Warehouse ​

For more complex data work, the KNIME Database (DB) Framework extends what you can do with Microsoft Fabric Warehouses beyond reading Delta tables. It lets you visually assemble SQL statements and push down complex data manipulations directly to the Fabric Data Warehouse compute engine — keeping processing in Fabric rather than loading data into KNIME.

Before you start ​

You need:

  • A Microsoft Fabric Workspace Connection (see Authenticate to Microsoft Fabric)

Connect ​

Use the Microsoft Fabric Data Warehouse Connector node to connect to a Data Warehouse within Microsoft Fabric.

  1. Add a Microsoft Fabric Data Warehouse Connector node.
  2. Connect the Microsoft Fabric Workspace Connection to its input port.
  3. Execute the node.

The output is a Database connection. Use it in nodes from the KNIME Database extension to query and manipulate data.

Read and modify data ​

  1. Connect the Database connection output from the Microsoft Fabric Data Warehouse Connector to a DB Table Selector node. Select the table you want to query or modify.
  2. Chain DB manipulation nodes to build your query logic visually. Each node builds a SQL query that executes on the Fabric side. Common nodes include:
    • DB Joiner
    • DB Row Filter
    • DB GroupBy
  3. Add a DB Reader node and execute it to run the assembled query in Fabric and import the result into KNIME.

Alternatively, use a DB Query Reader node to enter a SQL query directly and import the result.

For more on in-database processing, see the KNIME Database Extension Guide.

Load data ​

Use the DB Loader node to write data back to a Fabric Data Warehouse. Unlike the standard DB Writer, it uses database-specific bulk loading, which is significantly faster for large datasets.

The DB Loader requires a temporary staging area for data files. To configure it:

  1. Add the optional file system input port to the DB Loader node.
  2. Set the staging location using the Target folder option in the node configuration.
  3. Connect a file system connector to the optional input port — use the Azure Data Lake Storage Gen2 Connector or the Azure Blob Storage Connector.

INFO

OneLake is not supported as a staging area for the DB Loader node. Use Azure Data Lake Storage Gen2 or Azure Blob Storage instead.

Next steps ​

  • KNIME Database Extension Guide
  • See this example workflow on the KNIME Hub for an example of using a Fabric Data Warehouse with the KNIME Database framework.
Pager
Next pageInstallation