Page History

...

• Primary Key Strategy - see (DB_PRIMARY_KEY_STRATEGY Config Setting)
  • Sequential Integer Primary Key (SEQUENTIAL_INTEGER) is the best strategy for large loads. This allows the database to insert records into the index in a sequential manner, which is more efficient. If GUID strategy is used, records will be inserted into the index tree at random locations, resulting in index re-balancing after every insert.
• Hardware is very important to large content loads.
  • RRF Loads are loaded in a multi-threaded manner. Multi-processor servers will give the best performance.
  • If possible, seperate the database server and the loader server.
• Monitoring a load
  • Monitor all LexEVS logs (both 'load' and 'full' log).
  • If using MySQL, use INNODB tools to monitor Inserts per second. ( SHOW INNODB STATUS )

...

1. Start from an installed LexEVS local API.
   Image Removed Image Added
2. Load from <LexEVS root>/test/resources/testData/ the coding scheme Automobiles.xml (You should be able to do this using a source in any format supported for loading)
   Image Removed Image Added
3. Activate this scheme and view it's contents by getting a coded node set and resolving it.
   Image Removed Image Added
4. Load from <LexEVS root>/test/resources/testData/ the coding scheme testExtension.xml selecting the option to extend by selecting the Automobiles terminology from the drop down list by it's URN and version.
   Image Removed Image Added
5. View the concept codes for the extension and see both the original code set and the supplemental code set.
   Image Removed Image Added

Keep in mind that the testExtension.xml's file format can be used to extend any coding scheme currently loaded to LexEVS.

...