TSequentialGuidMode Enumeration

Specifies how the sequential timestamp bytes are placed within a generated GUID, optimizing index performance for different database engines.

Remarks

Different database engines sort and index GUID values differently depending on which bytes they consider significant. Choose the mode that matches the target database to ensure that sequentially generated GUIDs produce monotonically increasing index keys.

Syntax

Unit: Aurelius.Global.Utils

Members

Name	Value	Description
SequentialAtEnd	0	Sequential bytes are placed in the last 6 bytes of the GUID, suitable for databases that sort GUIDs by the trailing bytes (e.g., MySQL, PostgreSQL).
SequentialAsString	1	Sequential bytes are placed in the first bytes in string-display order, suitable for databases that sort GUIDs as strings (e.g., Oracle).
SequentialAsBinary	2	Sequential bytes are placed in the first bytes in binary storage order, suitable for databases that sort GUIDs by raw binary value (e.g., SQL Server).