Recently, due to the need for work, we began to focus on the relative optimization of select query statements for MySQL databases. Because of the actual project involved, it is found that when the data volume of MySQL table reaches millions, the efficiency of normal SQL query decreases linearly, and the query speed is simply intolerable if the query condition in where is more. Once tested on a table containing 400多万条 records (indexed) to perform a conditional query, its query time unexpectedly up to 40 seconds, I believe such a high query latency, any user will be crazy. So how to improve the efficiency of SQL statement query is very important. The following is an extensive network of 30 kinds of SQL query statement optimization method: 1, should try to avoid using the! = or <> operator in the WHERE clause, otherwise the engine discards the use of the index for a full table scan. 2, to optimize the query, should try to avoid full table scan, first of all should consider the where and order by the columns involved in the index. 3, should try to avoid the null value of the field in the Where clause to judge, otherwise it will cause the engine to abandon the use of the index for full table scan, such as: Select ID from t where num is null can set the default value of 0 on NUM, to ensure that the table NUM column does not have a null value, and then After this query: the Select ID from t where num=04, try to avoid using or in the WHERE clause to join the condition, otherwise it will cause the engine to abandon using the index for full table scan, such as: Select ID from t where num=10 or num =20 can query this way: The Select ID from the where num=10union allselect ID from T where num=205, the following query will also result in a full table scan: (cannot be the preceding percent) select ID from t whe Re name like '? c% ' to improve efficiency, you can consider full-text indexing. 6, in and not in also should be used with caution, otherwise it will cause a full table scan, such as: Select ID from the Where Num in (three-to-three) for a continuous value, can be used between do not use in: The Select ID from t where num Between 1 and 37, if parameters are used in the WHERE clause, can also cause a full table scan. Because SQL resolves local variables only at run time, the optimizer cannot defer the selection of access plans to run time; it must be selected at compile time. However, if an access plan is established at compile time, the value of the variable is still unknown, so it cannot beThe input selected for the index. The following statement will perform a full table scan: The select id from where [email protected] can be changed to force the query to use the index: SELECT ID from the T with (index name) where [Email&nbs P;protected]8, you should try to avoid expression operations on the field in the Where clause, which will cause the engine to abandon using the index for a full table scan. For example: Select ID from t where num/2=100 should be changed to: Select ID from t where num=100*29, should try to avoid function operation in the WHERE clause, which will cause the engine to abandon using the index for full table scan. such as: Select ID from t where substring (name,1,3) = ' abc ' –name idselect ID starting with ABC from t where DateDiff (Day,createdate, ' 2005-11-30′) =0– ' 2005-11-30′ generated ID should be changed to: Select ID from t where name like ' abc% ' select ID from t where crea Tedate>= ' 2005-11-30′ and createdate< ' 2005-12-1′10, do not perform functions, arithmetic operations, or other expression operations to the left of "=" in the WHERE clause, or the system may not use the index correctly. 11. When using an indexed field as a condition, if the index is a composite index, you must use the first field in the index as a condition to guarantee that the system uses the index, otherwise the index will not be used, and the field order should be consistent with the index order as much as possible. 12, do not write some meaningless queries, such as the need to generate an empty table structure: Select Col1,col2 into #t from T where 1=0 such code will not return any result set, but will consume system resources, should be changed to this: CREATE TABLE #t (...) 13, many times with exists instead of in is a good choice: Select num from a where num in (select num from B) is replaced with the following statement: Select Num from a where exisTS (select 1 from b where num=a.num) 14, not all indexes are valid for the query, SQL is query-optimized based on the data in the table, and when there is a large amount of data duplication in the index column, the SQL query may not take advantage of the index, as there are fields in the table Sex,male, Female almost every half of it, even building an index on sex does not work for query efficiency. 15, the index is not the more the better, although the index can improve the efficiency of the corresponding select, but also reduce the efficiency of insert and UPDATE, because the INSERT or update when the index may be rebuilt, so how to build the index needs careful consideration, depending on the situation. The number of indexes on a table should not be more than 6, if too many you should consider whether some of the indexes that are not commonly used are necessary. 16. You should avoid updating clustered index data columns as much as possible, because the order of the clustered index data columns is the physical storage order of the table records, which can consume considerable resources once the column values change to the order in which the entire table is recorded. If your application needs to update clustered index data columns frequently, you need to consider whether the index should be built as a clustered index. 17, try to use numeric fields, if only the value of the field is not designed as a character type, which will reduce the performance of query and connection, and increase storage overhead. This is because the engine compares each character in a string one at a time while processing queries and joins, and it is sufficient for a numeric type to be compared only once. 18, as far as possible to use Varchar/nvarchar instead of Char/nchar, because the first variable long field storage space is small, you can save storage space, and secondly for the query, in a relatively small field search efficiency is obviously higher. 19. Do not use SELECT * from t anywhere, replace "*" with a specific field list, and do not return any fields that are not available. 20. Try to use table variables instead of temporary tables. If the table variable contains a large amount of data, be aware that the index is very limited (only the primary key index). 21. Avoid frequent creation and deletion of temporary tables to reduce the consumption of system table resources. 22. Temporary tables are not unusable, and they can be used appropriately to make certain routines more efficient, for example, when you need to repeatedly reference a dataset in a large table or a common table. However, for one-time events, it is best to use an export table. 23. When creating a temporary table, if you insert a large amount of data at one time, you can use SELECT INTO instead of CREATE table to avoid causing a lot of log to improve the speed, if the amount of data is small, in order to mitigate the resources of the system table, create table First, Then insert. 24. IfWith temporary tables, it is important to explicitly delete all temporary tables at the end of the stored procedure, TRUNCATE table first, and then drop table, which avoids longer locking of the system tables. 25. Avoid using cursors as much as possible, because cursors are inefficient and should be considered for overwriting if the cursor is manipulating more than 10,000 rows of data. 26. Before using a cursor-based method or temporal table method, you should first look for a set-based solution to solve the problem, and the set-based approach is usually more efficient. 27. As with temporary tables, cursors are not unusable. Using Fast_forward cursors on small datasets is often preferable to other progressive processing methods, especially if you must reference several tables to obtain the required data. Routines that include "totals" in the result set are typically faster than using cursors. If development time permits, a cursor-based approach and a set-based approach can all be tried to see which method works better. 28. Set NOCOUNT on at the beginning of all stored procedures and triggers, set NOCOUNT OFF at the end. You do not need to send a DONE_IN_PROC message to the client after each statement that executes the stored procedure and trigger. 29, try to avoid the return of large data to the client, if the amount of data is too large, should consider whether the corresponding demand is reasonable.
Some ways to optimize query speed when MySQL handles massive amounts of data
