Documentation

sql.to() function

sql.to() writes data to an SQL database.

Function type signature
(
    <-tables: stream[A],
    dataSourceName: string,
    driverName: string,
    table: string,
    ?batchSize: int,
) => stream[A]

For more information, see Function type signatures.

Parameters

driverName

(Required) Driver used to connect to the SQL database.

Supported drivers:

  • bigquery
  • hdb
  • mysql
  • postgres
  • snowflake
  • sqlite3 (Does not work with InfluxDB OSS or InfluxDB Cloud)
  • sqlserver
  • vertica, vertigo

dataSourceName

(Required) Data source name (DNS) or connection string used to connect to the SQL database.

table

(Required) Destination table.

batchSize

Number of parameters or columns that can be queued within each call to Exec. Default is 10000.

If writing to SQLite database, set the batchSize to 999 or less.

tables

Input data. Default is piped-forward data (<-).


Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.7

Key enhancements in InfluxDB 3.7 and the InfluxDB 3 Explorer 1.5.

See the Blog Post

InfluxDB 3.7 is now available for both Core and Enterprise, landing alongside version 1.5 of the InfluxDB 3 Explorer UI. This release focuses on giving developers faster visibility into what their system is doing with one-click monitoring, a streamlined installation pathway, and broader updates that simplify day-to-day operations.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On February 3, 2026, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2