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

Register a JDBC driver ​

When KNIME Analytics Platform does not include a built-in driver for your database, you must register a vendor-specific JDBC driver manually. This makes the driver available for selection in the DB Connector node and dedicated connector nodes.

Before you begin ​

  • Obtain the JDBC driver from your database vendor. The driver must be JDBC 4.1 or later compliant.
  • The driver is typically provided as a .jar file. If provided as a .zip archive, extract it to a folder first.
  • If the driver requires native libraries (for example, DLLs), place all of them in a single folder alongside the .jar file.

For a list of common JDBC drivers, see JDBC driver reference.

Register the driver ​

Register the driver in the KNIME preferences to make it available in the connector nodes.

  1. In KNIME Analytics Platform, go to File → Preferences → KNIME → Databases.
  2. Click Add to open the new database driver dialog.
  3. Fill in the required fields:
    • ID — a unique identifier using only alphanumeric characters and underscores.
    • Name — a unique display name for the driver.
    • Description — a short description of the driver.
    • Database type — select the matching database type if it appears in the list. If your database is not listed, select default. Drivers registered as default are only available in the generic DB Connector node.
    • URL template — the JDBC connection URL format. If you selected a specific database type, a default template is pre-filled. Click the question mark icon for syntax guidance and examples.
    • Classpath — click Add file to select a single .jar file, or Add directory to select a folder containing multiple .jar files. If the driver requires native libraries, also add the folder containing them.
  4. Click Find driver classes to auto-detect the driver class. Select the correct class from the list.
  5. Click OK to save the driver.

TIP

Select a specific Database type when one is available. Drivers registered as default cannot be used with dedicated connector nodes — only with the generic DB Connector node.

Distribute drivers to Hub or Server executors ​

To make drivers available on KNIME Hub or KNIME Server executors, use a customization profile instead of registering manually on each machine. See Set up JDBC drivers on KNIME Hub and KNIME Server.

Next steps ​

  • Connect to a database with the generic DB Connector
  • Set up JDBC drivers on KNIME Hub and KNIME Server

Related pages ​

  • JDBC driver reference
  • Install a third-party database driver plug-in
Pager
Next pageInstallation