influxctl database update

The influxctl database update command updates a database’s retention period, table (measurement), or column limits in InfluxDB.

Usage

influxctl database update [flags] <DATABASE_NAME>

Arguments

Argument	Description
DATABASE_NAME	Name of the database to update

Flags

Flag		Description
	`--retention-period`	Database retention period (default is `0s` or infinite)
	`--max-tables`	Maximum tables per database (default is 500, 0 uses default)
	`--max-columns`	Maximum columns per table (default is 250, 0 uses default)
`-h`	`--help`	Output command help

Also see influxctl global flags.

Examples

Update a database’s retention period
Update a database’s table limit
Update a database’s column limit

Update a database’s retention period

influxctl database update --retention-period 1mo mydb

Valid durations units

m: minute
h: hour
d: day
w: week
mo: month
y: year

Example retention period values

0d: infinite/none
3d: 3 days
6w: 6 weeks
1mo: 1 month (30 days)
1y: 1 year
30d30d: 60 days
2.5d: 60 hours

Update a database’s table limit

influxctl database update --max-tables 300 mydb

Update a database’s column limit

influxctl database update --max-columns 200 mydb

Was this page helpful?

Thank you for your feedback!

Support and feedback

Thank you for being part of our community! We welcome and encourage your feedback and bug reports for InfluxDB Clustered and this documentation. To find support, use the following resources:

Customers with an annual or support contract can contact InfluxData Support.

Edit this page Submit docs issue

© 2026 InfluxData, Inc.

InfluxDB OSS 2.9.0: API tokens are hashed by default

Stronger token security in InfluxDB OSS 2.9.0 — tokens are hashed on disk by default. Existing tokens are hashed on first startup and can’t be recovered afterward. Capture any plaintext tokens you still need before you upgrade.

View InfluxDB OSS 2.9.0 release notes

Hashed tokens authenticate exactly like unhashed tokens — clients and integrations keep working.

Also new in 2.9.0:

Configurable backup compression
Restore support for backups containing hashed tokens
Tighter Edge Data Replication queue validation
Flux upgrade
Compaction reliability improvements

Key enhancements in Explorer 1.9

Explorer 1.9 is now available with InfluxQL support, an AI-assisted Flux to SQL converter (beta), and new live sample data simulators.

View Explorer 1.9 release notes

Explorer 1.9 includes new features and improvements that make it easier to query, visualize, and manage data.

Highlights:

Flux to SQL converter (beta): Convert Flux queries to SQL with an AI-assisted converter.
InfluxQL support: Query data with InfluxQL in the Data Explorer and dashboards, and save and load InfluxQL queries.
InfluxQL visualizations: Render line and bar charts from InfluxQL results with per-tag series grouping.
Query error history: Review a history of query errors in the query tool.
Live sample data simulators: Generate continuous live sample data with new bird data and signal generator simulators.

For more details, see Explorer 1.9 release notes

InfluxDB 3.10 is now available

InfluxDB 3 Core 3.10 adds an automatic catalog format upgrade, a configurable query-concurrency limit, and processing engine improvements.

Key updates in InfluxDB 3 Core 3.10:

Catalog format upgrade: the on-disk catalog automatically upgrades from format v2 to v3 on first 3.10 startup. Migration is one-way—back up your catalog before upgrading.
--max-concurrent-queries: limit concurrent queries (adjustable at runtime).
GET /ready endpoint for readiness probes.
Processing engine: cross-database queries and trigger lockdown flags.

For more information, see the InfluxDB 3 Core release notes.

InfluxDB 3.10 is now available

InfluxDB 3 Enterprise 3.10 adds automated backup and restore, row-level deletions, and user management, with an automatic catalog format upgrade and performance preview improvements.

Key updates in InfluxDB 3 Enterprise 3.10:

Catalog format upgrade: the on-disk catalog automatically upgrades from format v2 to v3 on first 3.10 startup. Migration is one-way—back up your catalog before upgrading.
Automated backup and restore (beta)
Row-level deletions
User management (authentication and RBAC) — preview
Performance preview improvements

Backup and restore, row-level deletions, and the performance preview require the Enterprise storage engine upgrade (opt-in beta). Beta and preview features are subject to breaking changes and aren’t recommended for production use.

For more information, see the InfluxDB 3 Enterprise release notes

Telegraf Enterprise is now generally available

Telegraf Enterprise is now generally available, along with Telegraf Controller v1.0.

Telegraf Enterprise combines Telegraf Controller, a centralized management console for Telegraf, with official support from InfluxData. Manage configurations, monitor fleet health, and operate tens of thousands of Telegraf agents from a single system.

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On September 15, 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