Logical record numbers in Btree databases are mutable in the face of record insertion or deletion. See Renumber for further discussion.

Maintaining record counts within a Btree introduces a serious point of contention, namely the page locations where the record counts are stored. In addition, the entire database must be locked during both insertions and deletions, effectively single-threading the database for those operations. Specifying UseRecordNumbers can result in serious performance degradation for some applications and data sets.

It is an error to specify UseRecordNumbers and anything other than NONE.

If the database already exists, the value of UseRecordNumbers must be the same as the existing database or an error is returned.