I have a Sql Server logging table, that continuously is being inserted into, I want to revise the design of this table.
Currently, we are using a GUID as the PK, because the software can generate this and we just insert it, and hopefully, multiple inserts won't block each other. However, UniqueId is not a very efficient PK for a table and our indexes are very large and fragmented.
If I change this column to a
auto-increment enabled. Will this become a concurrent insert bottleneck?
I do not need my primary key to be in any sort of order, Just a unique id for that row?