Which situations will cause “nested join” faster than “merge join”? (DBMR2559)

~ 0 min
2016-03-18 08:58

By default, if a table contains a small quantity of data, DBMaker will use “nested join” to query data. It scans part of data and takes less time. Conversely, if a table contains a great deal of data, DBMaker will use “merge join” to query data. It scans all data by scanning indexes and takes less time. However, if a table contains a great deal of data, and the SQL statements used to query data contains the clause “LIMIT”, the speed of querying data by using “merge join” is too slowly compared with “nested join”, so in this case, users, who use the version (of DBMaker 5.3) published after February 25, 2014, need to choose “nested join” by adding "DB_OPTRT = 1" into dmconfig.ini. This setting is available only for parts of query with LIMIT.

 

Version: DBMaker5.3.x

Product: Normal/Bundle

Platform: Windows/Linux

Average rating 0 (0 Votes)

You cannot comment on this entry

Tags