Load IBM Db2 data to Snowflake

Load IBM Db2 tables into Snowflake with dlt's sql_database source and your coding agent: the SQLAlchemy driver, connection string, table selection, and incremental loading.

SourceIBM Db2IBM Db2 is a family of relational database management systems, accessed from Python through IBM's SQLAlchemy adapter.Destination
Snowflake
Snowflake is a fully managed cloud data platform that runs on AWS, Azure and Google Cloud. Storage and compute scale independently, so warehouses can be resized or suspended per workload. dlt loads into Snowflake natively, handling schema evolution, incremental loading and staged file uploads.

IBM Db2 is a family of relational database management systems, accessed from Python through IBM's SQLAlchemy adapter. This page has everything needed to load IBM Db2 tables into Snowflake with dlt's sql_database source: the SQLAlchemy driver, the connection string, how to choose tables and load only new rows, plus the steps that hand the job to your coding agent.


Build your IBM Db2 to Snowflake pipeline

Set up a project, install the dltHub AI harness and its sql-database-pipeline toolkit, and let your coding agent build the pipeline:

uv init uv add "dlt[hub,sql_database,snowflake]" pyarrow pandas ibm-db-sa uv run dlthub ai init --agent <your-agent> # <agent>: claude | cursor | codex uv run dlthub ai toolkit install sql-database-pipeline

Then paste this prompt into Claude, Codex, or Cursor:

Prompt
Use /find-source to load tables from my IBM Db2 database into Snowflake.

The toolkit lists the schemas and tables in your database, asks which tables to load, then scaffolds a one-table pipeline and runs it with a load limit before scaling up. Credentials are inspected through MCP tools, so your agent never reads secrets.toml itself. About the toolkit →

Prefer to write it yourself? Every fact the agent uses is below.


IBM Db2 at a glance

dlt sourcesql_database (from dlt.sources.sql_database import sql_database)
SQLAlchemy driver nameibm_db_sa
Python driver packageibm-db-sa
Default port50000
Tables are grouped byschema (default: CURRENT_SCHEMA)
connectorx backendnot supported

How do I connect to IBM Db2?

dlt needs a database user with read access to the tables you want to load. Add its connection details to .dlt/secrets.toml:

[sources.sql_database.credentials] drivername = "ibm_db_sa" host = "localhost" port = 50000 username = "my_user" password = "my_password" database = "my_database"

Or as a single connection string:

[sources.sql_database] credentials = "ibm_db_sa://my_user:my_password@localhost:50000/my_database"

Use the ibm_db_sa SQLAlchemy dialect with the ibm_db/ibm_db_dbi driver. The driver requires IBM Db2 CLI client libraries to be available; for remote connections, install the IBM Data Server Driver Package and ensure its CLI library is accessible to the process.

Snowflake credentials go in the same file; the Snowflake destination docs list the fields it needs. dlt reads .dlt/secrets.toml automatically at runtime — never hardcode credentials in your pipeline script. For production, see setting up credentials with dlt.


Which IBM Db2 tables can I load into Snowflake?

Any table or view the database user can read. The sql_database source reads each table's schema from IBM Db2 and creates a matching table in Snowflake. These options narrow a load down to what you need:

To loadUse
A single tablesql_table(table="orders")
A specific schemasql_database(schema="CURRENT_SCHEMA")
Views as well as tablessql_database(include_views=True)
Only some columnssql_table(table="orders", included_columns=["id", "status"])
Only some rowssql_database(query_adapter_callback=...)

Always pass table_names=[...] to sql_database(): without it, dlt reflects every table in the schema before loading anything. IBM Db2 stores unquoted names in upper case, so a table created as orders is usually named ORDERS here.


How do I load only new IBM Db2 rows?

Give each table a cursor column and a primary key, and dlt loads only rows changed since the last run and merges them into Snowflake:

source.orders.apply_hints( incremental=dlt.sources.incremental("updated_at"), write_disposition="merge", primary_key="id", )

Use a timestamp such as updated_at for tables whose rows change, and an increasing id for append-only tables. On the first run dlt loads everything; after that it reads only rows past the last cursor value. See incremental loading.


What does the IBM Db2 to Snowflake pipeline look like?

This loads the customers and orders tables from the CURRENT_SCHEMA schema into Snowflake. Replace the table names with your own:

import dlt from dlt.sources.sql_database import sql_database def load_ibm_db2_to_snowflake() -> None: source = sql_database( schema="CURRENT_SCHEMA", table_names=["customers", "orders"], backend="pyarrow", ) source.orders.apply_hints( incremental=dlt.sources.incremental("updated_at"), write_disposition="merge", primary_key="id", ) pipeline = dlt.pipeline( pipeline_name="ibm_db2_pipeline", destination="snowflake", dataset_name="ibm_db2_data", ) load_info = pipeline.run(source) print(load_info) if __name__ == "__main__": load_ibm_db2_to_snowflake()

Credentials are not passed in the code: sql_database() reads them from [sources.sql_database] in .dlt/secrets.toml. Run it with uv run python ibm_db2_pipeline.py.


Which backend should I use?

The backend decides how rows are read from IBM Db2. The example uses pyarrow; switch if your data calls for it:

Data sizeBackendWhy
Under 100k rowssqlalchemy (default)No extra dependencies, runs dlt's full row-by-row normalization
100k – 10M rowspyarrow20–30× faster, keeps decimal and date types exact; needs numpy
Over 10M rowspyarrowconnectorx does not support IBM Db2

The toolkit's /optimize-sql-performance skill measures where time goes and picks a backend, chunk size and parallelism for you. See configuring the backend.


How do I query IBM Db2 data in Snowflake?

After a run, pipeline.dataset() holds the loaded tables. A Relation is a query on that dataset, either a whole table or a SQL string, and reading it gives you the data as a Pandas DataFrame, a PyArrow table or Python tuples. Nothing is read until you ask for it.

import dlt pipeline = dlt.pipeline("ibm_db2_pipeline") # Step 1: Get the dataset from the pipeline dataset = pipeline.dataset() # Step 2: Get a Relation, either a whole table... orders = dataset.table("orders") # ...or any SQL query against Snowflake recent = dataset("SELECT * FROM orders ORDER BY updated_at DESC LIMIT 100") # Step 3: Read the data df = orders.df() # or orders.df(chunk_size=50) for a large table arrow_table = recent.arrow() # a PyArrow Table rows = recent.fetchall() # a list of Python tuples

The columns are the ones of your IBM Db2 tables; dataset.row_counts().df() lists every table with its row count. Your agent can run the same queries through the MCP server's execute_sql_query tool, and uv run dlthub show opens the Pipeline Dashboard with the schema, load metrics and a query box. See access loaded data in Python and exploring it in marimo notebooks.


How do I deploy the IBM Db2 to Snowflake pipeline in production?

The pipeline runs locally, which is ideal for prototyping and one-off loads. When you need it on a schedule, monitored on every load, and shared with your team, deploy the same dlt code on the dltHub platform — no infrastructure to maintain. The harness's dlthub-platform toolkit takes your agent there:

uv run dlthub ai toolkit install dlthub-platform
  • Deploy & schedule — run the pipeline as a managed job with automatic retries.
  • Monitor — observable job queues, alerting, and load metrics for every run.
  • Transform — promote raw IBM Db2 loads into governed, documented models.
  • Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.

Book a demo →


What other destinations can I load IBM Db2 data to?

dlt loads into any of these — only the destination argument changes:

DestinationExample value
DuckDB"duckdb"
PostgreSQL"postgres"
BigQuery"bigquery"
Snowflake"snowflake"
Redshift"redshift"
Databricks"databricks"
Filesystem (S3, GCS, Azure)"filesystem"

Set dlt.pipeline(destination="snowflake") and add that destination's credentials in .dlt/secrets.toml. See the full destinations list.


Next steps

Was this page helpful?

Community Hub

Need more dlt context for IBM Db2 to Snowflake?

Request dlt skills, commands, AGENT.md files, and AI-native context.