Recommendations for the Data Table Definition
Last updated:2025-04-29 23:15:29
When designing a data table, you should follow certain guidelines and avoid common misunderstandings. For details, see the official documentation InfluxDB schema design and data layout. This article also provides suggestions for creating data tables to help you create the efficient TencentDB for CTSDB.
Database Table Naming
When defining the data table name of InfluxDB, you should use a meaningful name so that the content of the table can be easily identified and understood. The following are some suggestions for defining meaningful names:
Use descriptive names. For example, if you are storing sensor data, use the sensor name as the data table name.
Avoid using abbreviations or acronyms, as this may lead to confusion and unnecessary bewilderment.
Use lowercase letters and hyphens (-) to separate words, as this makes the names easier to read and understand.
When naming a data table, try to avoid using special characters, as this may lead to problems in queries and other operations.
Try to use short and concise names to avoid inputting too many characters in queries and other operations.
Tags and Fields
Tags are typically used to describe and identify data, such as device IDs, network addresses, and geographical locations. They help improve query performance and reduce the overhead of system resources. Tag values are used for filtering and grouping (such as GROUP BY) during queries. Therefore, unnecessary redundancy and nesting should be avoided when selecting tag values.
Fields are typically used to describe and record trends and changes in data, such as temperature, battery levels, traffic, and speed. Field values can be used for mathematical calculations and statistical analysis, including calculating averages, maximums, and minimums. Compared with tags, field values require aggregation and calculations, resulting in higher storage and query overhead, which in turn necessitates more CPU and memory resources.
Storing Data in Tags
In InfluxDB, tags are metadata used to identify and describe data. Storing data in tags can improve the database query performance and enable more effective data management and organization. The following are some suggestions for storing data in tags:
Store commonly used metadata: If a piece of data is metadata related to other data, such as sensor names, location information, or data sources, then store it in a tag. This makes querying and filtering data easier.
Use in GROUP BY(): If you plan to use certain data in a GROUP BY() statement, store it in a tag. By specifying the tag name in GROUP BY(), you can group the query results by the tag values.
Quick queries: If you need to perform a quick query on certain data, store it in a tag. Since tags are indexed, querying on tags is more efficient than querying on fields.
Storing Data in Fields
In InfluxDB, a field is an element used for storing data. Storing data in fields allows for easy use of InfluxQL functions and enables interpretation as types other than strings. The following are some suggestions for storing data in fields:
Store numeric data: If you need to perform numerical calculations or comparisons on data, store it in a field. This allows you to easily use InfluxQL functions to operate on the data.
Store timestamp data: If you need to perform time series analysis on data, store it in a field. InfluxDB supports timestamp fields and provides several functions for time series analysis.
Avoid storing duplicate data: If certain data has already been stored in a tag, there is no need to store it in a field again. This helps to avoid data duplication and improves query efficiency.
Use the correct data type: When defining a field, you should use the appropriate data type. For example, if you are storing numeric data, you should use a numeric field instead of a string field.
Grouping Data Fields
In InfluxDB, a field is an element used for storing data. When defining a data table, grouping fields into relevant measurement types helps to organize and manage data while improving query efficiency. The following are some suggestions for grouping fields:
Group by measurement type: Group fields with the same measurement type together. For example, if you are storing sensor data, you can group measurement types such as temperature, humidity, and pressure.
Use hyphens to separate words: When naming a field, use hyphens (-) rather than underscores (_) to separate words. Since underscores are used to separate fields and tags in InfluxDB, using hyphens (-) helps avoid confusion.
Organize the data table structure: When defining a data table, consider grouping fields with different measurement types into separate table structures. This helps better organize and manage data and improves query efficiency.
Query using wildcards: When querying, you can use wildcards to retrieve all fields of the same measurement type. For example, if you want to query all temperature fields, you can use the wildcard "*" to match all fields ending with "temp".
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No
Feedback