This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
intro:overview:where:largedb [2010/08/01 03:45] els created |
intro:overview:where:largedb [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ~~NOTOC~~ | ||
| {{page>:top_add&nofooter&noeditbtn}} | {{page>:top_add&nofooter&noeditbtn}} | ||
| ====== Introduction ====== | ====== Introduction ====== | ||
| - | [[intro:overview:where|Back to Introduction]] | + | [[intro:overview:what|What is Omnidex?]] | **[[intro:overview:where|Where is Omnidex Used?]]** | [[intro:overview:how|How is Omnidex Implemented?]] | [[intro:overview:demos|Watch Omnidex in Action]] |
| - | ====== Using Omnidex: Billion-record Databases ====== | + | ---- |
| + | ===== Where is Omnidex used? ===== | ||
| + | |||
| + | Omnidex is used in a wide variety of applications. Essentially, Omnidex is used when you need high performance and increased flexibility. Some of the more common Omnidex applications include: | ||
| + | |||
| + | * [[intro:overview:where:lists|Database marketing and customer lists]] | ||
| + | * [[intro:overview:where:analytics|Business analytics and data warehouses]] | ||
| + | * [[intro:overview:where:onlinedb|Online, searchable databases]] | ||
| + | * [[intro:overview:where:flatfiles|Transaction logs and raw data files]] | ||
| + | * [[intro:overview:where|Billion-record databases]] | ||
| + | |||
| + | == == | ||
| Businesses are always collecting more data. Today's challenge is to maintain fast searches on these large databases without breaking the bank. Omnidex's high-speed indexing is designed for very large databases. | Businesses are always collecting more data. Today's challenge is to maintain fast searches on these large databases without breaking the bank. Omnidex's high-speed indexing is designed for very large databases. | ||
| Line 15: | Line 27: | ||
| * **Reduce your footprint** - Omnidex's highly compressed indexes mean that you can maintain a small footprint, using less memory and disk storage while maintaining speed. | * **Reduce your footprint** - Omnidex's highly compressed indexes mean that you can maintain a small footprint, using less memory and disk storage while maintaining speed. | ||
| - | Billion-record databases are an asset, not a problem. Omnidex indexing allows business to capitalize on this asset, delivering fast performance and scalability. | + | Billion-record databases are an asset, not a problem. Omnidex indexing allows businesses to capitalize on this asset, delivering fast performance and scalability. |
| + | |||
| + | [[intro:overview:where| [close] ]] | ||
| + | |||
| + | ==== ===== | ||
| + | * [[intro:overview:where:text|Knowledgebases and text databases]] | ||
| + | |||
| + | ===== ===== | ||
| + | **[[intro:overview:how|Next]]** | ||
| - | **[[intro:overview:where|Prev]]** | ||
| {{page>:bottom_add&nofooter&noeditbtn}} | {{page>:bottom_add&nofooter&noeditbtn}} | ||
| + | |||
| + | |||