Talk:Query optimizer

Computing Redirect‑class

	This redirect is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing
Redirect	This redirect does not require a rating on Wikipedia's content assessment scale.

Databases (inactive)

This redirect is within the scope of WikiProject Databases, a project which is currently considered to be inactive.DatabasesWikipedia:WikiProject DatabasesTemplate:WikiProject DatabasesDatabases

The two imlementation sections use different terminology. That needs to be fixed.

The left-deep definition is still on the Join (SQL) page. That really should be pulled out and merged with the Tree traversal page somehow.

Derekian 17:26, 8 Jun 2005 (UTC)

In the Join ordering section, we see "This heuristic reduces the number of plans that need to be considered (n! instead of 4^n)", but n! increase faster than 4^n, did the author wanted the reverse ?

207.45.248.18 17:33, 18 January 2007 (UTC)[reply]

merge with query optimization?

There's a separate page on query optimization (which looks unfinished). Shouldn't they be merged? Eclecticos (talk) 04:23, 6 December 2007 (UTC)[reply]

Merge. I think that Query Optimizer be a sub section under Query Optimization. —Preceding unsigned comment added by 196.3.94.70 (talk) 15:48, 30 March 2009 (UTC)[reply]

Don't Merge. I think it should be left as such with just providing link in both pages to access each other. The query optimizer is the component of a database management system. Query optimization is the goal of technical rewriting/changing the query by either, the query optimizer, automated tuning software (e.g. query hints) or manual intervention (e.g. create index). In other words both are different encyclopedia entities which surround the same topic.

Merge. I think there is unlikely to be enough distinction between these two topics to merit two separate articles. For example, we don't have separate articles for pile driver and pile driving, nor for teacher and teaching, nor for editor and editing. --Doradus (talk) 01:59, 21 November 2009 (UTC)[reply]

Merge. I would rather see both under query optimization, but either way there shouldn't be two pages unless there's enough content to justify it. There is plenty to say about optimization but little to say about optimizers themselves. Although they are separate concepts we would essentially be reducing optimizers to a stub if we made them separate articles. 99.236.33.105 (talk)

Don't Merge. They should remain two separate topics. Optimization should be the advantages and disadvantages along with the theory behind different types of optimization. Optimizer should have all different types of actual optimizers. That being said, I think some of the content from Optimizer belongs in Optimization; however they should remain separate pages. Someone could add information about different optimizers used by different DBMS's, and the specifics about them. 137.99.14.134 (talk) 01:07, 27 April 2010 (UTC)Kralco626[reply]

Merge i up for merge ,,,cool 99.236.33.105 (talk)