Information générale
Catégorie:
Base de données, Tables, Vues, Index et syntaxe SQL
Hi,
Seek time is not something to worry about, is about the same.
I choosed the other way because I have three things, the PK, the timestamp of record creation (in sys(2015) and the workstation id, all in one column.
>>Hi Cetin
>>After 100000 inserts
>>
>>The index size is 2,994,176 bytes
>>
>>After Reindex is 2,161,152 bytes
>>
>>I think that is because are random generated.
>>From what I've read about B-tree indexes, this can be the cause.
>>
>>
>>
>Hi Dorin,
>I got a higher value (near 4Mb) but I don't think index size would be my main cause to choose or not to choose it. I wondered seek times. I never tried it myself thinking GUID's unicity is more valuable to me than the nanoseconds gained per seek.
>Cetin
Précédent
Suivant
Répondre
Voir le fil de ce thread
Voir le fil de ce thread à partir de ce message seulement
Voir tous les messages de ce thread
Voir tous les messages de ce thread à partir de ce message seulement