This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
admin:optimization:home [2012/02/01 19:17] doc |
admin:optimization:home [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 6: | Line 6: | ||
| ===== Introduction to Optimizing Queries ===== | ===== Introduction to Optimizing Queries ===== | ||
| - | |||
| **[[admin:optimization:home|Overview]]** | | **[[admin:optimization:home|Overview]]** | | ||
| - | [[admin:optimization:overview:plans|Plans]] | | + | [[admin:optimization:overview:plans|Query Plans]] | |
| - | [[admin:optimization:overview:hdc|Data Caches]] | | + | [[admin:optimization:overview:caches|Data Caches]] | |
| [[admin:optimization:overview:config|Configuring Omnidex]] | [[admin:optimization:overview:config|Configuring Omnidex]] | ||
| ---- | ---- | ||
| - | \\ | ||
| - | === Overview === | + | ==== Overview ==== |
| Omnidex specializes in query performance. Omnidex's first goal is to try to optimize the widest number of queries with the simplest installation. This allows administrators to develop, test and deploy applications as quickly as possible. Administrators usually place Omnidex or QuickText indexes on all of the columns involved in criteria, table joins, aggregations, grouping and ordering. Omnidex's SQL Engine then evaluates each statement and optimizes the query using the indexes available. This simple strategy optimizes a large number of queries. | Omnidex specializes in query performance. Omnidex's first goal is to try to optimize the widest number of queries with the simplest installation. This allows administrators to develop, test and deploy applications as quickly as possible. Administrators usually place Omnidex or QuickText indexes on all of the columns involved in criteria, table joins, aggregations, grouping and ordering. Omnidex's SQL Engine then evaluates each statement and optimizes the query using the indexes available. This simple strategy optimizes a large number of queries. | ||
| Line 26: | Line 24: | ||
| That being said, Omnidex also has it's collection of optimization techniques. Like the underlying database, some of these may involved denormalizing tables or adjusting the SQL statement. Other times, it simply requires using indexing techniques that are highly specific to a particular performance issue. This section will describe these techniques, but keep in mind that the first step is always to understand what the query was originally trying to accomplish, and optimize that problem whenever possible. | That being said, Omnidex also has it's collection of optimization techniques. Like the underlying database, some of these may involved denormalizing tables or adjusting the SQL statement. Other times, it simply requires using indexing techniques that are highly specific to a particular performance issue. This section will describe these techniques, but keep in mind that the first step is always to understand what the query was originally trying to accomplish, and optimize that problem whenever possible. | ||
| - | The first step to improving optimization is to understand [[admin:optimization:overview:plans|Omnidex Query Plans]]. | + | The first step to improving optimization is to understand the [[admin:optimization:overview:plans|Omnidex query plans]]. |
| - | + | ||
| - | + | ||
| - | [[admin:optimization:plans:home| More >]] | + | |
| ===== ===== | ===== ===== | ||
| Line 39: | Line 34: | ||
| ====== Additional Resources ====== | ====== Additional Resources ====== | ||
| See also: | See also: | ||
| - | {{page>:admin:indexing:see_also&nofooter&noeditbtn}} | + | {{page>:admin:optimization:see_also&nofooter&noeditbtn}} |
| {{page>:bottom_add&nofooter&noeditbtn}} | {{page>:bottom_add&nofooter&noeditbtn}} | ||