# Resolution of Hotspots in Nonclustered Index
```
CREATE TABLE sbtest1(                      CREATE TABLE sbtest1(
 ~!@id int(11) NOT NULL,                       id int(11) NOT NULL,@!~
 k int(11) NOT NULL DEFAULT '0',            k int(11) NOT NULL DEFAULT '0',
 c char(120) NOT NULL DEFAULT ",   ---->    c char(120) NOT NULL DEFAULT ",
 pad CHAR(60) DEFAULT " NOT NULL,           pad CHAR(60) DEFAULT " NOT NULL,
 PRIMARY KEY (id) NOCLUSTERED               ~!@PRIMARY KEY (id) NOCLUSTERED@!~
)                                          )~!@SHARD_ROW_ID_BITS =4,PRE_SPLIT_REGIONS=2@!~

CREATE TABLE sbtest1(                      CREATE TABLE sbtest1(
 id int(11) NOT NULL,                       id int(11) NOT NULL,
 k int(11) NOT NULL DEFAULT '0',            k int(11) NOT NULL DEFAULT '0',
 c char(120) NOT NULL DEFAULT ",   ---->    c char(120) NOT NULL DEFAULT ",
 pad CHAR(60) DEFAULT " NOT NULL,           pad CHAR(60) DEFAULT " NOT NULL,
 ~!@NOCLUSTERED                                NOCLUSTERED@!~
)                                          )~!@SHARD_ROW_ID_BITS =4,PRE_SPLIT_REGIONS=2@!~
```

| 4 bits | 60 bits           |
| :----- | :---------------- |
| random | implicit tuple ID |

----------------------------------------------------
In summary, our solution to the hotspots issue in Nonclustered Index is to set two properties, SHARD_ROW_ID_BITS and PRE_SPLIT_REGIONS, for the table. This prevents the formation of hotspots when inserting a large amount of data under high concurrency.