Merge pull request #5573 from influxdata/5568-clustered-docs-need-to-be-updated-claim-hard-limit-of-250-columns-per-database

5568 clustered docs need to be updated claim hard limit of 250 columns per database

Author: jstirnaman

.ci/vale/styles/Google/Units.yml

@@ -5,4 +5,5 @@ nonword: true
 level: error
 tokens:
   - \b\d+(?:B|kB|MB|GB|TB)
-  - \b\d+(?:ns|ms|s|min|h|d)
+# Ignore duration literals in code blocks.
+  - \b(?!\`)\d+(?:ns|ms|s|min|h|d)

content/influxdb/cloud-dedicated/admin/databases/_index.md

@@ -11,6 +11,14 @@ menu:
     parent: Administer InfluxDB Cloud
 weight: 101
 influxdb/cloud-dedicated/tags: [databases]
+related:
+  - /influxdb/cloud-dedicated/write-data/best-practices/schema-design/
+  - /influxdb/cloud-dedicated/reference/cli/influxctl/
+alt_links:
+  cloud: /influxdb/cloud/admin/buckets/
+  cloud_serverless: /influxdb/cloud-serverless/admin/buckets/
+  clustered: /influxdb/cloud-dedicated/admin/databases/
+  oss: /influxdb/v2/admin/buckets/
 ---
 
 An InfluxDB database is a named location where time series data is stored.
@@ -19,11 +27,13 @@ Each InfluxDB database has a [retention period](#retention-periods).
 {{% note %}}
 **If coming from InfluxDB v1**, the concepts of databases and retention policies
 have been combined into a single concept--database. Retention policies are no
-longer part of the InfluxDB data model. However, InfluxDB Cloud Dedicated does
+longer part of the InfluxDB data model.
+However, {{% product-name %}} does
 support InfluxQL, which requires databases and retention policies.
 See [InfluxQL DBRP naming convention](/influxdb/cloud-dedicated/admin/databases/create/#influxql-dbrp-naming-convention).
 
-**If coming from InfluxDB v2 or InfluxDB Cloud**, _database_ and _bucket_ are synonymous.
+**If coming from InfluxDB v2, InfluxDB Cloud (TSM), or InfluxDB Cloud Serverless**,
+_database_ and _bucket_ are synonymous.
 {{% /note %}}
 
 ## Retention periods
@@ -40,9 +50,10 @@ never be removed by the retention enforcement service.
 
 ## Table and column limits
 
-In {{< product-name >}}, table (measurement) and column limits can be
-customized when [creating](#create-a-database) or
-[updating a database](#update-a-database).
+You can customize [table (measurement) limits](#table-limit) and
+[table column limits](#column-limit) when you
+[create](#create-a-database) or
+[update a database](#update-a-database) in {{< product-name >}}.
 
 ### Table limit
 
@@ -60,7 +71,8 @@ cluster in the following ways:
 {{% expand "**May improve query performance** <em style='opacity:.5;font-weight:normal;'>View more info</em>" %}}
 
 Schemas with many measurements that contain
-[focused sets of tags and fields](/influxdb/cloud-dedicated/write-data/best-practices/schema-design/#design-for-performance) can make it easier for the query engine to
+[focused sets of tags and fields](/influxdb/cloud-dedicated/write-data/best-practices/schema-design/#design-for-performance)
+can make it easier for the query engine to
 identify what partitions contain the queried data, resulting in better
 query performance.
 
@@ -72,7 +84,7 @@ data by measurement and time range and stores each partition as a Parquet
 file in your cluster's object store. By increasing the number of measurements
 (tables) you can store in your database, you also increase the potential for
 more `PUT` requests into your object store as InfluxDB creates more partitions.
-Each `PUT` request incurs a monetary cost and will increase the operating cost of
+Each `PUT` request incurs a monetary cost and increases the operating cost of
 your cluster.
 
 {{% /expand %}}
@@ -91,20 +103,33 @@ operating cost of your cluster.
 
 **Default maximum number of columns**: 250
 
-Time, fields, and tags are each represented by a column in a table.
+**Configurable maximum number of columns**: 1000
+
+Each row must include a time column, with the remaining columns representing
+tags and fields.
+As a result, a table with 250 columns can have one time column and up to
+249 field and tag columns.
+
+If you attempt to write to a table and exceed the column limit, the write
+request fails and InfluxDB returns an error.
+
+If you update the column limit for a database, the limit applies to newly
+created tables; doesn't override the column limit for existing tables.
+
 Increasing your column limit affects your {{% product-name omit=" Clustered" %}}
 cluster in the following ways:
 
 {{< expand-wrapper >}}
-{{% expand "May adversely affect query performance" %}}
-
-At query time, the InfluxDB query engine identifies what table contains the queried
-data and then evaluates each row in the table to match the conditions of the query.
-The more columns that are in each row, the longer it takes to evaluate each row.
-
-Through performance testing, InfluxData has identified 250 columns as the
-threshold where query performance may be affected
-(depending on the shape of and data types in your schema).
+{{% expand "May adversely affect system performance" %}}
+
+When creating or updating a database, you can configure the table column limit to be
+lower than the default or up to 1000, based on your requirements.
+InfluxData identified 250 columns as the safe limit for maintaining system
+performance and stability.
+Exceeding this threshold can result in
+[wide schemas](/influxdb/cloud-dedicated/write-data/best-practices/schema-design/#avoid-wide-schemas),
+which can negatively impact performance and resource use,
+depending on your queries, the shape of your schema, and data types in the schema.
 
 {{% /expand %}}
 {{< /expand-wrapper >}}

content/influxdb/cloud-dedicated/admin/databases/update.md

@@ -57,9 +57,11 @@ to update a database in your {{< product-name omit=" Clustered" >}} cluster.
 
     - Database name
     - _Optional_: Database [retention period](/influxdb/cloud-dedicated/admin/databases/#retention-periods).
-    Default is infinite (`0`).
-    - _Optional_: Database table (measurement) limit. Default is `500`.
-    - _Optional_: Database column limit. Default is `250`.
+      Default is infinite (`0`).
+    - _Optional_: Database [table (measurement) limit](/influxdb/cloud-dedicated/admin/databases/#table-limit).
+      Default is `500`.
+    - _Optional_: Database [column limit](/influxdb/cloud-dedicated/admin/databases/#column-limit).
+      Default is `250`.
 
 {{% code-placeholders "DATABASE_NAME|30d|500|200" %}}
 

content/influxdb/cloud-dedicated/query-data/troubleshoot-and-optimize/optimize-queries.md

@@ -15,31 +15,31 @@ related:
   - /influxdb/cloud-dedicated/query-data/execute-queries/analyze-query-plan/
 aliases:
   - /influxdb/cloud-dedicated/query-data/execute-queries/optimize-queries/
+  - /influxdb/cloud-dedicated/query-data/execute-queries/analyze-query-plan/
 ---
 
 Optimize SQL and InfluxQL queries to improve performance and reduce their memory and compute (CPU) requirements.
 Learn how to use observability tools to analyze query execution and view metrics.
 
 - [Why is my query slow?](#why-is-my-query-slow)
 - [Strategies for improving query performance](#strategies-for-improving-query-performance)
+  - [Query only the data you need](#query-only-the-data-you-need)
 - [Analyze and troubleshoot queries](#analyze-and-troubleshoot-queries)
 
 ## Why is my query slow?
 
 Query performance depends on time range and complexity.
 If a query is slower than you expect, it might be due to the following reasons:
 
-- It queries data from a  large time range.
+- It queries data from a large time range.
 - It includes intensive operations, such as querying many string values or `ORDER BY` sorting or re-sorting large amounts of data.
 
 ## Strategies for improving query performance
 
 The following design strategies generally improve query performance and resource use:
 
 - Follow [schema design best practices](/influxdb/cloud-dedicated/write-data/best-practices/schema-design/) to make querying easier and more performant.
-- Query only the data you need--for example, include a [`WHERE` clause](/influxdb/cloud-dedicated/reference/sql/where/) that filters data by a time range.
-  InfluxDB v3 stores data in a Parquet file for each measurement and day, and retrieves files from the Object store to answer a query.
-  The smaller the time range in your query, the fewer files InfluxDB needs to retrieve from the Object store.
+- [Query only the data you need](#query-only-the-data-you-need).
 - [Downsample data](/influxdb/cloud-dedicated/process-data/downsample/) to reduce the amount of data you need to query.
 
 Some bottlenecks may be out of your control and are the result of a suboptimal execution plan, such as:
@@ -52,9 +52,41 @@ Some bottlenecks may be out of your control and are the result of a suboptimal e
 {{% note %}}
 #### Analyze query plans to view metrics and recognize bottlenecks
 
-To view runtime metrics for a query, such as the number of files scanned, use the [`EXPLAIN ANALYZE` keywords](/influxdb/cloud-dedicated/reference/sql/explain/#explain-analyze) and learn how to [analyze a query plan](/influxdb/cloud-dedicated/query-data/troubleshoot-and-optimize/analyze-query-plan/).
+To view runtime metrics for a query, such as the number of files scanned, use
+the [`EXPLAIN ANALYZE` keywords](/influxdb/cloud-dedicated/reference/sql/explain/#explain-analyze)
+and learn how to [analyze a query plan](/influxdb/cloud-dedicated/query-data/troubleshoot-and-optimize/analyze-query-plan/).
 {{% /note %}}
 
+### Query only the data you need
+
+#### Include a WHERE clause
+
+InfluxDB v3 stores data in a Parquet file for each partition.
+By default, {{< product-name >}} partitions tables by day, but you can also
+[custom-partition your data](/influxdb/cloud-dedicated/admin/custom-partitions/).
+At query time, InfluxDB retrieves files from the Object store to answer a query.
+To reduce the number of files that a query needs to retrieve from the Object store,
+include a [`WHERE` clause](/influxdb/cloud-dedicated/reference/sql/where/) that
+filters data by a time range or by specific tag values.
+
+#### SELECT only columns you need 
+
+Because InfluxDB v3 is a columnar database, it only processes the columns
+selected in a query, which can mitigate the query performance impact of
+[wide schemas](/influxdb/cloud-dedicated/write-data/best-practices/schema-design/#avoid-wide-schemas).
+
+However, a non-specific query that retrieves a large number of columns from a
+wide schema can be slower and less efficient than a more targeted
+query--for example, consider the following queries:
+
+- `SELECT time,a,b,c`
+- `SELECT *`
+
+If the table contains 10 columns, the difference in performance between the
+two queries is minimal.
+In a table with over 1000 columns, the `SELECT *` query is slower and
+less efficient.
+
 ## Analyze and troubleshoot queries
 
 Use the following tools to analyze and troubleshoot queries and find performance bottlenecks:

content/influxdb/cloud-dedicated/reference/cli/influxctl/database/create.md

@@ -102,9 +102,9 @@ influxctl database create [flags] <DATABASE_NAME>
 
 | Flag |                         | Description                                                                                                                              |
 | :--- | :---------------------- | :--------------------------------------------------------------------------------------------------------------------------------------- |
-|      | `--retention-period`    | Database retention period (default is `0s`, 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)                                                                               |
+|      | `--retention-period`    | [Database retention period ](/influxdb/cloud-dedicated/admin/databases/#retention-periods)(default is `0s`, infinite)                                                                                    |
+|      | `--max-tables`          | [Maximum tables per database](/influxdb/cloud-dedicated/admin/databases/#table-limit) (default is 500, `0` uses default)                                                                             |
+|      | `--max-columns`         | [Maximum columns per table](/influxdb/cloud-dedicated/admin/databases/#column-limit) (default is 250, `0` uses default)                                                                               |
 |      | `--template-tag`        | Tag to add to partition template (can include multiple of this flag)                                                                     |
 |      | `--template-tag-bucket` | Tag and number of buckets to partition tag values into separated by a comma--for example: `tag1,100` (can include multiple of this flag) |
 |      | `--template-timeformat` | Timestamp format for partition template (default is `%Y-%m-%d`)                                                                          |

content/influxdb/cloud-dedicated/reference/cli/influxctl/database/update.md

@@ -14,6 +14,8 @@ table (measurement), or column limits in InfluxDB.
 
 ## Usage
 
+<!-- pytest.mark.skip -->
+
 ```sh
 influxctl database update [flags] <DATABASE_NAME>
 ```
@@ -28,9 +30,9 @@ influxctl database update [flags] <DATABASE_NAME>
 
 | 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)   |
+|      | `--retention-period` | [Database retention period ](/influxdb/cloud-dedicated/admin/databases/#retention-periods)(default is `0s` or infinite)        |
+|      | `--max-tables`       | [Maximum tables per database](/influxdb/cloud-dedicated/admin/databases/#table-limit) (default is 500, 0 uses default) |
+|      | `--max-columns`      | [Maximum columns per table](/influxdb/cloud-dedicated/admin/databases/#column-limit) (default is 250, 0 uses default)   |
 | `-h` | `--help`             | Output command help                                          |
 
 {{% caption %}}