Icon

KNIME Table Connector components

Demonstration workflow for utilising KNIME Table Connector components.

Connect an H2 Connector to the first KNIME Table Connector and then pass this connection through to subsequent connectors so that they all use the same DB session.

Configure each connector with its own KNIME input data and then you can easily run SQL queries against those KNIME tables

As it is not possible to put OPTIONAL input ports on a KNIME Component, there are two versions of theKNIME Table ConnectorThe KNIME Table Session Connector creates its own in-memory H2 database connection and providesthis on the output port for use by subsequent KNIME Table Connector components which require a DBSession to be supplied. This ensures that KNIME sees they are all using the same session, allowing theIn-Database nodes (e.g. DB Joiner) to work with all of them The alternative is to add your own H2 Connector and simply chain this to a KNIME Table Connector,which can chain to subsequent KNIME Table Connectors.This means you have to add the specific H2 connector node, but does allow you to modify theconfiguration such as making it write to disk, rather than being in-memory if this is more suitable foryour requirement. Initial Connector if noprevious sessionEmployeesDepartmentEmp DeptOr just write a custom queryto join the tables3 tablesSelect basedon the DB JoinersA simple queryof EmployeesDepartmentWrite your custom querytAlternativelysupply an H2 sessionvia a connector KNIME TableSession Connector Table Creator Table Creator Table Creator DB Joiner DB Query Reader DB Reader DB Joiner KNIME TableConnector DB Query Reader Table Creator KNIME TableConnector DB Query Reader H2 Connector KNIME TableConnector As it is not possible to put OPTIONAL input ports on a KNIME Component, there are two versions of theKNIME Table ConnectorThe KNIME Table Session Connector creates its own in-memory H2 database connection and providesthis on the output port for use by subsequent KNIME Table Connector components which require a DBSession to be supplied. This ensures that KNIME sees they are all using the same session, allowing theIn-Database nodes (e.g. DB Joiner) to work with all of them The alternative is to add your own H2 Connector and simply chain this to a KNIME Table Connector,which can chain to subsequent KNIME Table Connectors.This means you have to add the specific H2 connector node, but does allow you to modify theconfiguration such as making it write to disk, rather than being in-memory if this is more suitable foryour requirement. Initial Connector if noprevious sessionEmployeesDepartmentEmp DeptOr just write a custom queryto join the tables3 tablesSelect basedon the DB JoinersA simple queryof EmployeesDepartmentWrite your custom querytAlternativelysupply an H2 sessionvia a connectorKNIME TableSession Connector Table Creator Table Creator Table Creator DB Joiner DB Query Reader DB Reader DB Joiner KNIME TableConnector DB Query Reader Table Creator KNIME TableConnector DB Query Reader H2 Connector KNIME TableConnector

Nodes

Extensions

Links

Download

To use this workflow in KNIME, download it from the below URL and open it in KNIME:

Download Workflow
Created by: bbate
Created at: 2023-07-07
On NodePit since: 2023-07-07
Last update: 2026-01-27
Created with KNIME version: v4.7.8
Tags: KNIME DBJoin

Deploy, schedule, execute, and monitor your KNIME workflows locally, in the cloud or on-premises – with our brand new NodePit Runner.

Try NodePit Runner!