2020-04-03 13:23:32 +00:00
---
2022-08-28 14:53:34 +00:00
slug: /en/engines/table-engines/special/set
2022-04-09 13:29:05 +00:00
sidebar_position: 60
sidebar_label: Set
2020-04-03 13:23:32 +00:00
---
2022-06-02 10:55:18 +00:00
# Set Table Engine
2017-04-03 19:49:50 +00:00
2020-06-10 20:14:51 +00:00
A data set that is always in RAM. It is intended for use on the right side of the `IN` operator (see the section “IN operators”).
2017-04-03 19:49:50 +00:00
2020-06-10 20:14:51 +00:00
You can use `INSERT` to insert data in the table. New elements will be added to the data set, while duplicates will be ignored.
But you can’ t perform `SELECT` from the table. The only way to retrieve data is by using it in the right half of the `IN` operator.
2017-04-03 19:49:50 +00:00
2020-06-10 20:14:51 +00:00
Data is always located in RAM. For `INSERT` , the blocks of inserted data are also written to the directory of tables on the disk. When starting the server, this data is loaded to RAM. In other words, after restarting, the data remains in place.
2017-04-03 19:49:50 +00:00
2017-04-26 17:26:17 +00:00
For a rough server restart, the block of data on the disk might be lost or damaged. In the latter case, you may need to manually delete the file with damaged data.
2017-12-28 15:13:23 +00:00
2020-11-06 11:23:04 +00:00
### Limitations and Settings {#join-limitations-and-settings}
When creating a table, the following settings are applied:
2023-01-06 22:01:28 +00:00
#### persistent
Disables persistency for the Set and [Join ](/docs/en/engines/table-engines/special/join.md/#join ) table engines.
Reduces the I/O overhead. Suitable for scenarios that pursue performance and do not require persistence.
Possible values:
- 1 — Enabled.
- 0 — Disabled.
Default value: `1` .