In releases prior to 5.2.1, the unique identifiers assigned to objects were generated using an algorithm that produces completely random values. In the 5.2.1 release, a new algorithm is available that produces sequential IDs. Sequential IDs have a time- and counter-based portion that is combined with a random portion in such a way that consecutively created IDs are sequential (monotonic) per the natural ordering applied by the underlying database.
The new UseSequentialIds property on the ObjectStore interface specifies whether an object store should assign random or sequential IDs when a new object is created in that object store. An indexed database column or a table with a clustered index on the primary key containing sequential IDs might be stored more compactly and managed more efficiently than completely random IDs, hence potentially providing a performance benefit and space savings.
The default value for this property is true (assign sequential IDs). If you do not want new objects in an object store to have sequential IDs, set the value of the UseSequentialIds property to false.
The GUID that you obtain from the ACCE or through APIs are different looking than that of the object_id stored in the database tables as bit reversal is used.
It's not recommend to insert value manually into database. Use ACCE/APIs to trigger the events.