[SOLVED]

For the first time I came across a database with a considerable growth (**125.000 inserts/day**).

This database is used to keep track of equipments of a Network.

I have many data related to those equipments and I'll be updating them day2day (checking if they were upgraded/downgraded/changed position/got unninstalled and thousands of stuff) SO means that I need to constantly Update them and the only fixed thing Would be their serialnumbers.

Now my headache begins...

I have a useless **ID [int(11) PK)**, It's useless because everything I do is based on **SerialNumbers [varchar(22) UQ]**.

Looking further I saw that serialnumbers are always HEX from (7 to 24) places, first thing in my mind was: TADA solved, just put those serialnumbers as integer and work everytime with hex2dec conversions nothing fancy... Then I figured out that unsigned bigints wasn't enough for numbers larger than HEX(16).

And finally, the question:

> 
> Anyone have any idea about which is the fastest indexable way to store
>  my SerialNumber fields?
> 
> 
> 

I don't mind if you didn't try the solution you're about to say, any idea would be welcome and Upvoted :) 

The picture below shows a count of serialnumbers for each SerialNumber lenght I have in the database.
[![enter image description here](https://i.stack.imgur.com/Mqk6m.png)](https://i.stack.imgur.com/Mqk6m.png)