Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
admin:optimization:plans:optimization [2012/02/03 20:14]
doc
admin:optimization:plans:optimization [2016/06/28 22:38] (current)
Line 160: Line 160:
 ==== Further Optimization === ==== Further Optimization ===
  
-A query is considered "fully optimized"​ when there are no wanted ​warnings or notes in the query plan.  ​Moreover, the goal is always ​to process as much of the query in the Omnidex indexes as possible, and to access the underlying database as little as possible. ​ It is not uncommon ​for extremely complex queries to be processed entirely in the Omnidex indexes, with no access to the underlying database, even when there are many table joins, subqueries, complex criteria, aggregations and ordering.  ​+A query is considered "fully optimized"​ when there are no unwanted ​warnings or notes in the query plan.  ​The goal with Omnidex optimization ​is to process as much of the query in the Omnidex indexes as possible, and to access the underlying database as little as possible. ​ It is even possible ​for extremely complex queries to be processed entirely in the Omnidex indexes, with no access to the underlying database, even when there are many table joins, subqueries, complex criteria, aggregations and ordering.  ​
  
 Sometimes the techniques described above are not enough to achieve the desired query performance. ​ Some queries will perform poorly because of the fundamental structure of the query. ​ This can happen because the query is written in an unusual way, often using techniques that are recommended for an underlying relational database. ​ It is sometimes best to study the query, understand what the query is fundamentally trying to do, and then simplify the query.  ​ Sometimes the techniques described above are not enough to achieve the desired query performance. ​ Some queries will perform poorly because of the fundamental structure of the query. ​ This can happen because the query is written in an unusual way, often using techniques that are recommended for an underlying relational database. ​ It is sometimes best to study the query, understand what the query is fundamentally trying to do, and then simplify the query.  ​
  
-Other times, it is beneficial to restructure the query to take advantage of Omnidex indexing techniques, similar to what may have been done the underlying relational database. It is usually preferable to maintain queries in their simplest form, but like all databases, certain approaches work better than others.+While simplicity is usually the best approach for Omnidex optimizationthere are times when it is beneficial to restructure the query to take advantage of Omnidex indexing techniques.  Ironicallythis is similar to what may have been done for an underlying relational database, but this time we are favoring the optimization techniques of Omnidex 
  
-If you are not able to achieve the level of performance you desired with a query, contact Technical Support. ​ We can sometimes offer suggestions as part of your support contract, and if needed, we can discuss having an engineer ​analysis ​your environment and your query plans to achieve improved performance. ​+If you are not able to achieve the level of performance you desired with a query, contact ​[[appendix:​contactus|Technical Support]].  We can sometimes offer suggestions as part of your support contract, and if needed, we can discuss having an engineer ​analyze ​your environment and your query plans to achieve improved performance. ​
  
  
Line 178: Line 178:
 ====== 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}}
 
Back to top
admin/optimization/plans/optimization.1328300062.txt.gz ยท Last modified: 2016/06/28 22:38 (external edit)