JDBC gateway concept
Instead of embedding drivers in every worker, the gateway:- Hosts driver isolation per database type and version
- Pools connections with configurable limits
- Translates Planasonix SQL requests into JDBC calls your database understands
- Surfaces errors back to pipeline logs with JDBC SQLState context
Supported databases
The JDBC path supports many engines when you supply a compatible driver. Common enterprise examples include:
Exact support depends on driver licensing—your legal team must approve redistribution if drivers are not publicly downloadable.
Driver upload
1
Obtain the JAR
Download from the vendor or your internal artifact repository; verify checksums.
2
Upload in admin console
Navigate to Connectors → JDBC gateway → Drivers and upload with a descriptive label (
teradata-17.20-jdbc4).3
Create a connection template
Supply JDBC URL pattern, default properties, and credential mapping.
4
Test connectivity
Run
SELECT 1 from a privileged admin account, then validate least-privilege service accounts for pipelines.Operational guidance
Network paths
Network paths
Open firewall rules from gateway hosts to database listeners; avoid NAT ambiguity with multi-subnet clusters.
Secrets
Secrets
Store passwords and keytabs in your vault; rotate on the same schedule as native DB users.
Performance
Performance
Tune fetch size and parallel readers based on DBA guidance; JDBC defaults are rarely optimal for ETL throughput.
Related topics
Connections overview
How credentials and networking fit together.
SQL assistance
Author JDBC-backed SQL with Copilot help.