This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
admin:admin:applications:prototype [2011/01/24 15:26] 127.0.0.1 external edit |
admin:admin:applications:prototype [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ~~NOTOC~~ | ~~NOTOC~~ | ||
| + | |||
| {{page>:top_add&nofooter&noeditbtn}} | {{page>:top_add&nofooter&noeditbtn}} | ||
| Line 6: | Line 7: | ||
| ===== Building Omnidex Applications ===== | ===== Building Omnidex Applications ===== | ||
| - | [[admin:admin:applications:design|Design]] -> **[[admin:admin:applications:prototype|Prototype]]** -> [[admin:admin:applications:development|Development]] -> [[admin:admin:applications:testing|Testing]] -> [[admin:admin:applications:staging|Staging]] -> [[admin:admin:applications:production|Production]] -> [[admin:admin:applications:optimization|Optimization]] | + | [[admin:admin:applications:design|Design]] | **[[admin:admin:applications:prototype|Prototype]]** | [[admin:admin:applications:development|Development]] | [[admin:admin:applications:testing|Testing]] | [[admin:admin:applications:staging|Staging]] | [[admin:admin:applications:production|Production]] | [[admin:admin:applications:optimization|Optimization]] |
| ---- | ---- | ||
| Line 26: | Line 27: | ||
| Administrators usually create a small test database, often using an Omnidex Snapshot. This test database is useful for optimizing queries and predicting performance. Since Omnidex Snapshots reside in flat files, they are highly portable and can be moved to development servers. They do not require licenses for the relational database software, nor do they need the support of database administrators. This allows Omnidex prototyping to occur quickly and easily, without affecting the main data server. | Administrators usually create a small test database, often using an Omnidex Snapshot. This test database is useful for optimizing queries and predicting performance. Since Omnidex Snapshots reside in flat files, they are highly portable and can be moved to development servers. They do not require licenses for the relational database software, nor do they need the support of database administrators. This allows Omnidex prototyping to occur quickly and easily, without affecting the main data server. | ||
| - | Omnidex Snapshots can be built on a subset of the database. At this stage of analyzing queries, the database does not need more than a few thousand rows. A smaller database allows quick changes to the indexing structure as queries are tuned, avoiding the complications of indexing the main database. Omnidex Snapshots can be built using the Omnidex Administrator. For more information on Omnidex Snapshots, refer to the article on [[admin:snapshots:home|Omnidex Snapshots]]. | + | Omnidex Snapshots can be built on a subset of the database. At this stage of analyzing queries, the database does not need more than a few thousand rows. A smaller database allows quick changes to the indexing structure as queries are tuned, avoiding the complications of indexing the main database. Omnidex Snapshots can be built using the Omnidex Administrator. For more information on Omnidex Snapshots, refer to the article on [[admin:features:snapshots:home|Omnidex Snapshots]]. |
| The production database can be indexed directly as long as the development and testing process does not interfere with regular operations. If the database contains over 20 million rows, it is a candidate for an Omnidex Grid; therefore, a smaller database would be appropriate for prototyping. | The production database can be indexed directly as long as the development and testing process does not interfere with regular operations. If the database contains over 20 million rows, it is a candidate for an Omnidex Grid; therefore, a smaller database would be appropriate for prototyping. | ||
| Line 32: | Line 33: | ||
| === 2. Creating an Omnidex Environment === | === 2. Creating an Omnidex Environment === | ||
| - | Omnidex databases are described in an Omnidex Environment. Omnidex Environments store information about the underlying database, the Omnidex indexing and other configuration settings. Omnidex Environments can then be connected to using a variety of tools and API's. | + | Omnidex databases are described in an Omnidex Environment. Omnidex Environments store information about the underlying database, the Omnidex indexing and other configuration settings. Omnidex Environments can then be connected to a variety of tools and API's. |
| Omnidex Environments are created interactively using the Omnidex Administrator, or are created with SQL statements such as CREATE ENVIRONMENT, CREATE DATABASE, CREATE TABLE and CREATE INDEX. Both of these approaches will create an XML file that contains all of the meta-data describing an Omnidex-enhanced database. | Omnidex Environments are created interactively using the Omnidex Administrator, or are created with SQL statements such as CREATE ENVIRONMENT, CREATE DATABASE, CREATE TABLE and CREATE INDEX. Both of these approaches will create an XML file that contains all of the meta-data describing an Omnidex-enhanced database. | ||
| - | The [[admin:environments:home|Omnidex Environments]] section of the documentation discusses how to create and connect to Omnidex Environments. | + | The [[admin:basics:environments:home|Omnidex Environments]] section of the documentation discusses how to create and connect to Omnidex Environments. |
| === 3. Creating Omnidex Indexes === | === 3. Creating Omnidex Indexes === | ||
| Line 46: | Line 47: | ||
| Omnidex indexes can be built interactively using the Omnidex Administrator, or can be built using the UPDATE INDEXES statement. | Omnidex indexes can be built interactively using the Omnidex Administrator, or can be built using the UPDATE INDEXES statement. | ||
| - | The [[admin:indexing:create|Creating Omnidex Indexes]] section of the documentation discusses how to create and build Omnidex indexes. | + | The documentation on [[admin:indexing:creation:home|Index Creation]] discusses how to create and build Omnidex indexes. |
| === 4. Optimizing Queries === | === 4. Optimizing Queries === | ||
| Line 60: | Line 61: | ||
| === 5. Prototyping the Application === | === 5. Prototyping the Application === | ||
| - | Once the queries are optimized, a broader prototype can be creating that engages any client-side functionality. Omnidex is most commonly accessed using standard ODBC and JDBC drivers. Omnidex provides its own Network Services optimized to Omnidex's needs. | + | Once the queries are optimized, a broader prototype can be created that engages any client-side functionality. Omnidex is most commonly accessed using standard ODBC and JDBC drivers. Omnidex provides its own Network Services optimized to Omnidex's needs. |
| Application architectures often contain many other layers such as analytic tools, bus interfaces, intermediate languages, middleware tools, load balancers, connection poolers, etc. Omnidex will integrate by simply pointing to the Omnidex ODBC or JDBC driver rather than the relational database's ODBC or JDBC driver. Some tailoring may be needed in the application layers to take advantage of Omnidex's extended functionality, such as fuzzy searches or geographic searches. | Application architectures often contain many other layers such as analytic tools, bus interfaces, intermediate languages, middleware tools, load balancers, connection poolers, etc. Omnidex will integrate by simply pointing to the Omnidex ODBC or JDBC driver rather than the relational database's ODBC or JDBC driver. Some tailoring may be needed in the application layers to take advantage of Omnidex's extended functionality, such as fuzzy searches or geographic searches. | ||