4 ms·
What is a "sequential GUID"?
by eridius 15y ago
What is a "sequential GUID"?
- dspillett 15y agoThis is where you start with a UUID that is as random as usual, but subsequent UUIDs for that same field are sequential rather than each being random relative to each other. This makes them a little faster to generate (though the significance of this is likely minute compared to the cost of writing them to disk except in very specific cases) and makes index maintenance operations more likely to produce efficient results (fewer split pages, less need to defragment the indexes later, and so forth). Another possible advantage of "sequential" UUIDs comes when a number of them get transmitted in a textual form, for instance if they are product IDs and you are sending out a long HTML page of links to products. The sequential IDs will offer more redundancy for any transport level compression to chew on than the normal random ones (assuming they are indeed sufficiently random) will. This may also come into play if your database engine supports compressed storage directly, as MSSQL 2008 does for backups (std and enterprise editions) and live data files (ent edition only), though to a much lesser extent unless the compression algorithm chosen is specifically optimal for small variations in to 128-bit aligned data.