This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
install:releases:odx50 [2011/01/05 18:05] els |
install:releases:odx50 [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ~~NOTOC~~ | ||
| {{page>:top_add&nofooter&noeditbtn}} | {{page>:top_add&nofooter&noeditbtn}} | ||
| - | ====== Software Installation ====== | + | ====== Software Installation: Release Notes ====== |
| - | + | ||
| - | ===== What's New with Omnidex? ===== | + | |
| Each new version of Omnidex brings a collection of improvements, from new features to increased performance. Here are the primary features and enhancements in the major releases of Omnidex: | Each new version of Omnidex brings a collection of improvements, from new features to increased performance. Here are the primary features and enhancements in the major releases of Omnidex: | ||
| Line 9: | Line 8: | ||
| - | ==== Omnidex 5.0 (July 2009) ===== | + | ===== Omnidex 5.0 (July 2009) ====== |
| - | === Simpler and Higher-Performing Indexing === | + | ==== Simpler and Higher-Performing Indexing ==== |
| Omnidex 5.0 combines all indexing features into one index type, simplifying the installation of indexes and greatly speeding index builds. Earlier versions of Omnidex used separate index types for searching and aggregating. Criteria was generally optimized with MDK indexes, and aggregations were generally optimized with ASK indexes. This frequently required administrators to index some columns twice, once with each index type, thus increasing build time and system resources. Indexes suitable for aggregations and ordering were also built individually, requiring many scans of the underlying data. Omnidex 5.0 allows all indexes to be processed in one batch. In heavily indexed scenarios, this can result in a 500% improvement in build performance and a 50% reduction in disk space. | Omnidex 5.0 combines all indexing features into one index type, simplifying the installation of indexes and greatly speeding index builds. Earlier versions of Omnidex used separate index types for searching and aggregating. Criteria was generally optimized with MDK indexes, and aggregations were generally optimized with ASK indexes. This frequently required administrators to index some columns twice, once with each index type, thus increasing build time and system resources. Indexes suitable for aggregations and ordering were also built individually, requiring many scans of the underlying data. Omnidex 5.0 allows all indexes to be processed in one batch. In heavily indexed scenarios, this can result in a 500% improvement in build performance and a 50% reduction in disk space. | ||
| - | === Support for XML Environment Files === | + | ==== Support for XML Environment Files ==== |
| Omnidex 5.0 introduces XML files as the new storage approach for Omnidex Environment Files. Historically, Omnidex Environment Files were created by compiling a source file into an Environment File. Omnidex 5.0 now records all information in a highly versatile and portable XML file. Compiled Environment Files are still supported for backward compatibility; however, new features will be developed using the new XML format. | Omnidex 5.0 introduces XML files as the new storage approach for Omnidex Environment Files. Historically, Omnidex Environment Files were created by compiling a source file into an Environment File. Omnidex 5.0 now records all information in a highly versatile and portable XML file. Compiled Environment Files are still supported for backward compatibility; however, new features will be developed using the new XML format. | ||