---
title: Local SQLDB Development and Larger Database Imports and Exports Now Available
canonical: https://telnyx.com/release-notes/sqldb-local-development-larger-imports-exports
---
# Local SQLDB Development and Larger Database Imports and Exports Now Available

[View as page](https://telnyx.com/release-notes/sqldb-local-development-larger-imports-exports)

[Release notes](https://telnyx.com/release-notes)

# Local SQLDB Development and Larger Database Imports and Exports Now Available

### 3, Nov 2026

Developers can now build and validate [SQLDB](https://telnyx.com/products/sqldb)\-backed Edge Compute applications locally, and manage larger database backups with new export and import workflows in the `telnyx-edge` CLI.

### What's new

* **Local SQLDB development (CLI v0.5.12+):** Run SQL queries and database migrations locally without modifying a deployed database. Local SQLDB runs in Docker on the same SQL engine as the deployed runtime, and databases persist between sessions under `.telnyx/sqldb/` by default. Because `telnyx-edge dev` and local SQLDB commands access the same local database configured in `telnyx.toml`, you can test schema changes and functions together before deployment. Docker is required for local SQLDB commands.
* **Larger exports, up to 4 GiB (CLI v0.5.15+):** Export a SQL dump up to 4 GiB, including schema-only, data-only, or specific-table output, to back up a database or move data between environments.
* **A dedicated import workflow, up to 100 MiB (CLI v0.5.16+):** `storage sqldb import` loads a SQL dump from a local file or a previous export, without splitting files to fit the roughly 4 MiB limit on remote `execute --file` requests. Imports run as jobs, the CLI reports progress, and interrupting the CLI wait does not cancel a running import.

### Why it matters

Database-backed Edge Compute workflows previously required iterating against a deployed database and splitting large SQL files to fit remote execution limits. With local development and higher export and import limits, you can test schema changes and functions locally, export database dumps up to 4 GiB for backups, and restore dumps up to 100 MiB through the new import workflow instead of splitting large SQL files into small remote execution requests.

Local SQLDB is isolated from production: local changes are not automatically synced or deployed. Export and import limits are independent: a dump larger than 100 MiB can be exported, but it cannot be restored through the new import command. Imports apply in atomic batches; if a later batch fails, earlier successful batches remain applied.

### Getting started

1. Run a local query and apply migrations:

telnyx-edge storage sqldb execute DB --local --command "SELECT 1"
telnyx-edge storage sqldb migrations apply DB --local

1. Export a database and import it elsewhere:

telnyx-edge storage sqldb export <database-id> --remote --output ./database.sql
telnyx-edge storage sqldb import <database-id> --file ./database.sql

**Learn more** in the [SQLDB CLI guide](https://developers.telnyx.com/docs/edge-compute/sqldb/cli), the [SQLDB migrations guide](https://developers.telnyx.com/docs/edge-compute/sqldb/migrations), and the [SQLDB limits reference](https://developers.telnyx.com/docs/edge-compute/sqldb/limits).

[Start building](https://telnyx.com/sign-up)