--- updatedAt: 2025-10-30T22:24:27.000Z agentTools: projectIndex: https://docs.wizata.com/llms.txt --- # Multi-bucket support on queries As explained in our [article on buckets](https://docs.wizata.com/docs/connect-data-time-series-structure#buckets), InfluxDB 2.x and above supports the use of multiple buckets. While the default bucket configured in the system is used automatically, there are several ways to query data from other buckets. # Data Stores Starting version 11.1, **Data stores** allow you to organize time-series data in separate containers, making it easier to manage operations like backup, migration, restore and deletion. > For more information, refer to [our dedicated article.](https://docs.wizata.com/reference/data-stores) If your datapoint is already linked to the correct data store, you can normally query your data **without having to specify a`bucket` parameter inside it**. ## "Do Not Use `sensorId`" option When creating a new Data Store entity, you will encounter a `doNotUserSensorId` checkbox. By default, the system links time-series data through the tag `sensorId`, **which must match the datapoint’s** `hardwareId`. > Check [Fields and Tags for more information](https://docs.wizata.com/docs/connect-data-time-series-structure#fields-and-tags) If you uncheck this option, the platform will instead **use the default field-based mapping to match the hardwareId**.

# Extra tags in datapoints As an alternative, you can also specify the **bucket** and **measurement** directly in the **datapoint’s hardwareId** This is useful when querying data stored in a non-default bucket or measurement. To do this, format the hardware ID as `[bucket][measurement]my_datapoint` For example, if your data is stored in bucket `database` and measurement `sensors`, the `hardwareId` should be `[database][sensors]my_datapoint`