Cause Analysis and Solution of slow SQL query speed, and cause analysis of slow SQL query speed

Cause Analysis and Solution of slow SQL query speed, and cause analysis of slow SQL query speed

Cause Analysis and Solution for slow SQL query speed

There are many reasons for slow query speed. The following are common causes:
　　
1. No index or no index is used (this is the most common problem of slow query and is a defect in programming)
　　
2. Low I/O throughput, resulting in a bottleneck effect.
　　
3. the query is not optimized because no computing column is created.
　　
4. Insufficient memory
　　
5. slow network speed
　　
6. The queried data volume is too large (you can use multiple queries to reduce the data volume in other ways)
　　
7. Lock or deadlock (this is also the most common problem of slow query and is a defect in programming)
　　
8. sp_lock and sp_who are active users. The reason is that they read and write competing resources.
　　
9. Unnecessary rows and columns are returned.
　　
10. The query statement is not good and is not optimized.

You can optimize the query by using the following methods:
　　
1. Place data, logs, and indexes on different I/O devices to increase the reading speed. In the past, Tempdb can be placed on RAID0, which is not supported by SQL2000. The larger the data size (size), the more important it is to increase I/O.
　　
2. vertically and horizontally split the table to reduce the table size (sp_spaceuse)
　　
3. upgrade hardware
　　
4. Create an index based on the query conditions, optimize the index, optimize the access mode, and limit the data volume of the result set. Note that the fill factor should be appropriate (preferably the default value 0 ). The index should be as small as possible. Use a column with a small number of bytes to create an index (refer to the index creation). Do not create a single index for fields with a limited number of values, such as gender fields.
　　
5. Improve network speed;
　　
6. Expand the server memory. Windows 2000 and SQL server2000 support 4-8 GB memory. Configure virtual memory: the virtual memory size should be configured based on services running concurrently on the computer. Run Microsoft SQLServer? 2000, you can consider setting the virtual memory size to 1.5 times the physical memory installed on your computer. If you have installed the full-text search feature and intend to run the Microsoft Search Service for full-text indexing and query, consider: set the virtual memory size to at least three times the physical memory installed on the computer. Configure the SQLServer max server memory server configuration option to 1.5 times the physical memory (half the virtual memory size ).
　　
7. Increase the number of server CPUs. However, you must understand that resources such as memory are more required for concurrent processing of serial processing. Whether to use parallelism or serial travel is automatically evaluated and selected by MsSQL. A single task is divided into multiple tasks and can be run on the processor. For example, if the sort, connection, scan, and GROUPBY statements of delayed queries are executed simultaneously, SQLSERVER determines the optimal parallel level based on the system load, complex queries that consume a large amount of CPU are most suitable for parallel processing. However, Update, Insert, and Delete operations cannot be processed in parallel.
　　
8. If you use like for query, you cannot simply use index, but the full-text index consumes space. Like 'a % 'when the index like' % a' is used and like '% a %' is not used for the query, the query time is proportional to the total length of the field value, so the CHAR type cannot be used, but VARCHAR. Create a full-text index for a long field value.
　　
9. Separate DB Server and APPLication Server; Separate OLTP and OLAP
　　
10. Distributed partition view can be used to implement Database Server consortium. A consortium is a group of separately managed servers, but they collaborate to share the processing load of the system. This mechanism of forming Database Server consortium through partition data can expand a group of servers to support the processing needs of large multi-layer Web sites. For more information, see designing a database federation server. (Refer to the SQL Help File 'partition view ')
　　
A. before implementing the partition view, a horizontal partition table must be created.
　　
B. After creating a member table, define a distributed partition view on each Member Server, and each view has the same name. In this way, queries that reference the view name of a distributed partition can run on any Member Server. System operations are the same as if each member server has a copy of the original table, but in fact each server has only one member table and a distributed partition view. The data location is transparent to the application.
　　
11. Rebuild the index dbcc reindex, dbcc indexdefrag, shrink data and log dbcc shrinkdb, and DBCCSHRINKFILE. set automatic log shrinking. for large databases, do not set Automatic database growth, which will reduce the server performance. The writing of T-SQL is very important. The following lists common points: first, the process of DBMS processing the query plan is as follows:
　　
1. query statement lexical and syntax check
　　
2. submit the statement to the query optimizer of the DBMS.
　　
3. optimizer performs algebra optimization and access path optimization
　　
4. A query plan is generated by the Pre-compilation module.
　　
5. Then, submit it to the system for processing and execution at the appropriate time.
　　
6. Finally, return the execution result to the user. Next, let's take a look at the data storage structure of SQLSERVER: the size of a page is 8 K (8060) bytes, and 8 pages are a disk area, store data in the Tree B.
　　
12. Difference Between Commit and rollback Rollback: Roll back all things. Commit: Submit the current transaction. there is no need to write things in dynamic SQL. If you want to write things, write them out, such as begin tran exec (@ s) commit trans, or write dynamic SQL into functions or stored procedures.
　　
13. Use the Where clause in the Select statement to limit the number of returned rows to avoid table scanning. If unnecessary data is returned, the server's I/O resources are wasted, this increases the burden on the network and reduces performance. If the table is large, the table is locked during the table scan and other connections are prohibited from accessing the table. The consequence is serious.
　　
14. SQL statement comments have no impact on execution
15. Try not to use the cursor. It occupies a large amount of resources. If you need row-by-row execution, try to use non-cursor technology, such as loop on the client, using temporary tables, Table variables, subqueries, and Case statements. The cursor can be classified according to the extraction options it supports: only the rows must be extracted from the first row to the last row. Fetch next is the only allowed extraction operation and is also the default method. You can extract arbitrary rows randomly anywhere in the cursor. The cursor technology becomes very powerful in SQL2000, and its purpose is to support loops. There are four concurrent options READ_ONLY: Update cannot be located through the cursor, and there is no lock in the rows that make up the result set. OPTIMISTIC WITHvalueS: OPTIMISTIC Concurrency Control is a standard part of transaction control theory. Optimistic Concurrency control is used in this case. In the interval between opening the cursor and updating the row, there is only a small chance for the second user to update a row. When a cursor is opened with this option, there is no lock to control the rows, which will help maximize its processing capability. If you try to modify a row, the current value of the row is compared with the value obtained from the last row extraction. If any value changes, the server will know that the other person has updated the row and will return an error. If the value is the same, the server executes the modification. Select this concurrency option optimisticwith rowversioning: this optimistic concurrency control option is based on Row version control. Use row version control. The table must have a version identifier, which can be used by the server to determine whether the row is changed after the cursor is read. In SQL Server, this performance is provided by the timestamp data type. It is a binary number that indicates the relative sequence of changes in the database. Each database has a global current timestamp value: @ DBTS. Every time you change a row with a timestamp column in any way, SQL Server first stores the current @ DBTS value in the timestamp column, and then adds the value of @ DBTS. If a table has a timestamp column, the timestamp is recorded as a row. The server can compare the current timestamp value of a row with the timestamp value stored during the last extraction to determine whether the row has been updated. The server does not need to compare the values of all columns. You only need to compare the timestamp column. If the application requires Optimistic Concurrency Based on Row Version Control for tables without a timestamp column, the cursor is optimistic concurrency control based on the value by default. Scroll locks implements pessimistic concurrency control. In pessimistic concurrency control, when the row of the database is read into the cursor result set, the application attempts to lock the row of the database. When a server cursor is used, an update lock is placed on the row when it is read into the cursor. If the cursor is opened in the transaction, the update lock of the transaction will be kept until the transaction is committed or rolled back. When the next row is extracted, the cursor lock will be removed. If the cursor is opened outside the transaction, the lock is discarded when the next row is extracted. Therefore, whenever you need full pessimistic concurrency control, the cursor should be opened in the transaction. The update lock prevents any other task from obtaining the update lock or exclusive lock, thus preventing other tasks from updating the row. However, the update lock does not prevent the shared lock, so it does not prevent other tasks from reading rows, unless the second task also requires reading with the update lock. Based on the lock prompts specified in the Select statement defined by the cursor, these cursor concurrency options can generate a scroll lock. The scroll lock is obtained on each row during extraction and is kept until the next extraction or cursor is closed. The first occurrence prevails. During the next extraction, the server obtains the scroll lock for the Newly Extracted row and releases the scroll lock of the last extracted row. The rolling lock is independent of the transaction lock and can be kept after a commit or rollback operation. If the option to close the cursor when submitting is off, the COMMIT statement does not close any opened cursor, and the scroll lock is retained until it is committed to maintain isolation of the extracted data. The type of the obtained scroll lock depends on the cursor concurrency option and the lock prompt in the Select statement of the cursor. Lock prompt read-only optimistic value optimistic row version control lock No prompt not locked update NOLOCK not locked HOLDLOCK sharing update UPDLOCK error Update TABLOCKX Error unlocked unlocked update other unlocked update * The specified NOLOCK prompt will make the table specified with this prompt read-only in the cursor.
　　
16. Use Profiler to track the query, obtain the time required for the query, and locate the SQL problem. Use the index optimizer to optimize the index.
　　
17. Pay attention to the difference between UNion and UNion all. Good UNION all
　　
18. Use DISTINCT unless necessary. Similar to UNION, it slows down the query. Duplicate records are no problem in the query.
　　
19. Do not return unwanted rows or columns during query.
　　
20. Use sp_configure 'query governor cost limit 'or SETQUERY_GOVERNOR_COST_LIMIT to limit the resources consumed by the query. When the resource consumed by the evaluation query exceeds the limit, the server automatically cancels the query and kills the query before the query. Set locktime: SET the lock time.
　　
21. Use select top 100/10 Percent to limit the number of rows returned by the user or SETROWCOUNT to limit the rows to be operated.
　　
22. Before SQL2000, do not use the following words: "is null", "<> ","! = ","!> ","! <"," NOT "," not exists "," not in "," not like ", and" LIKE '% 100' ", because they do NOT leave the index and are all table scans. Do not add a function to the column name in the Where clause, such as Convert and substring. If a function is required, create a computed column and then create an index. you can also use a work und: replace WhereSUBSTRING (firstname,) = 'M' with Where firstname like'm % '(index scan). Be sure to separate the function from the column name. In addition, the index cannot be too large or too large. Not in scans the table multiple times and replaces it with EXISTS, NOTEXISTS, IN, and left outer join, especially the left join. Exists is faster than IN, and the slowest operation is NOT. if the column value is null, its index does not work in the past. Now the 2000 optimizer can process it. The same ISNULL, "NOT", "not exists", "NOTIN" can optimize her, but "<>" and so on cannot be optimized and indexes are NOT used.
　　
23. Use QueryAnalyzer to check the SQL statement query plan and evaluate and analyze whether the SQL statement is optimized. Generally, 20% of the Code occupies 80% of the resources, and our optimization focuses on these slow points.
　　
24. If the in or query is not indexed, use the display statement to specify the INDEX: Select * FROM PersonMember (INDEX = IX_Title) Where processid IN ('male ', female ')
　　
25. Pre-calculate the results to be queried and place them in the table. Select the results when querying. This was the most important method before SQL7.0. For example, hospital hospitalization fee calculation.
　　
26. Appropriate indexes can be used for MIN () and MAX.
　　
27. There is a principle in the database that the code is closer to the data, the better. Therefore, the Default is the preferred one, which is Rules, Triggers, and Constraint (constraints such as the external key CheckUNIQUE ......, The maximum length of the data type, etc. are constraints), Procedure. This not only requires low maintenance work, high programming quality, and fast execution speed.
　　
28. If you want to Insert a large binary value to the Image column, use the stored procedure. Do not Insert the value using an embedded Insert Statement (whether JAVA is used or not ). In this way, the application first converts the binary value to a string (twice the size of the string), and then converts it to a binary value after the server receives the character. the stored procedure does not have these actions: Method: Create procedure p_insert as insert into table (Fimage) values (@ image), and calls this stored procedure on the foreground to pass in binary parameters, this significantly improves the processing speed.
　　
29. Between is faster IN some cases than IN, and Between can locate the range based on the index faster. Use the query optimizer to see the difference. Select * from chineseresume where title in ('male', 'female ') Select * fromchineseresume where between 'male' and 'female' are the same. Because in may be more than once, it may be slower sometimes.
　　
30. If it is necessary to create an index for a global or local temporary table, it may increase the speed, but not necessarily because the index also consumes a lot of resources. Its creation is the same as that of the actual table.
　　
31. Do not create useless things, such as wasting resources when generating reports. Use it only when necessary.
　　
32. The OR clause can be divided into multiple queries and connected to multiple queries through UNION. Their speed is only related to whether an index is used. If a query requires a joint index, UNIONall is more efficient. no index is used for multiple OR statements, and it is rewritten to the form of UNION to try to match the index. Whether or not indexes are used in a key issue.
　　
33. Use a view as little as possible, which is less efficient. Operations on a view are slower than operations on a table. You can replace it with storedprocedure. In particular, do not use nested views. nested views increase the difficulty of searching for original data. Let's look at the essence of the View: it is an optimized SQL statement stored on the server that has produced a query plan. When retrieving data from a single table, do not use a view pointing to multiple tables. Read data directly from the view that only contains the table. Otherwise, unnecessary overhead is added, the query is disturbed. to speed up View query, MsSQL adds the View index function.
　　
34. Do not use DISTINCT or order by unless necessary. These actions can be executed on the client. They increase additional overhead. This is the same as UNION and union all.
　　
Select top 20ad. companyname, comid, position, ad. referenceid, worklocation, convert (varchar (10), ad. postDate, 120) aspostDate1, workyear, degreedescription into ad where referenceIDin ('jcnad00329667 ', 'jcnad132168', 'jcnad00337748', 'jcnad00338345 ',
'Jcnad00333138 ', 'jcnad00303570', 'jcnad00303569 ',
'Jcnad00303568 ', 'jcnad00306698', 'jcnad00231935 ', 'jcnad00231933 ',
'Jcnad00254567', 'jcnad00254585 ', 'jcnad00254608 ',
'Jcnad00254607 ', 'jcnad00258524', 'jcnad00332379', 'jcnad00268618 ',
'Jcnad00279196 ', 'jcnad00268613') order by postdate desc
　　
35. IN the post-IN nominal value list, place the most frequent values at the beginning and the least value at the end to reduce the number of judgments.
　　
36. When SelectINTO is used, it locks the system table (sysobjects, sysindexes, etc.) and blocks access from other connections. When creating a temporary table, use the show statement instead of select. drop table t_lxh begin tran select * into t_lxh fromchineseresume where -- commit in another connection Select * from sysobjects You Can See That Select INTO locks the system table, create table also locks the system table (whether it is a temporary table or a system table ). So never use it in things !!! In this case, use real tables or temporary table variables for temporary tables that are frequently used.
　　
37. Generally, redundant rows can be removed before group by having clauses, so try not to use them for row removal. Their execution sequence should be optimal as follows: select Where clause Selects all appropriate rows, Group By is used to Group statistical rows, and Having clause is used to remove redundant groups. In this way, the consumption of Group By Having is small, and queries are fast. Grouping and Having large data rows consumes a lot of resources. If the purpose of GroupBY is not to include computing, but to group, it is faster to use Distinct.
　　
38. Updating multiple records at a time is faster than updating multiple records at a time, that is, batch processing is good.
　　
39. Use less temporary tables and replace them with result sets and Table variables. Table variables are better than temporary tables.
　　
40. In SQL2000, calculated fields can be indexed. The following conditions must be met:
　　
A. The expression of calculated fields is definite.
　　
B. Data Types of TEXT, Ntext, and Image cannot be used.
　　
C. The following options must be prepared: ANSI_NULLS = ON, ANSI_PADDINGS = ON ,.......
　　
41. Try to put data processing on the server to reduce network overhead, such as using stored procedures. Stored procedures are compiled, optimized, organized into an execution plan, and stored in the database as SQL statements. They are a collection of control flow languages and are fast. You can use a temporary stored procedure to execute dynamic SQL statements repeatedly. This process (temporary table) is stored in Tempdb. In the past, due to SQL Server's lack of support for complex mathematical computing, we had to put this job on another layer to increase network overhead. SQL2000 supports UDFs and now supports complex mathematical computing. the return value of a function is not too large, which is costly. User-Defined Functions consume a large amount of resources like the cursor. If a large result is returned, the stored procedure is used.
　　
42. Do not use the same function repeatedly in one sentence, waste resources, and put the result in a variable before calling it faster.
　　
43. The efficiency of Select COUNT (*) is low. Try to change his writing style as much as possible, while EXISTS is fast. note the difference: the returned values of selectcount (Field of null) from Table and select count (Field of NOT null) from Table are different !!!
　　
44. When the server has enough memory, the number of preparation threads = the maximum number of connections + 5, which can maximize the efficiency; otherwise, use the number of prepared threads <maximum number of connections to enable the SQL SERVER thread pool. If the number is equal to the maximum number of connections + 5, the performance of the SERVER is seriously damaged.
　　
45. Access your table in a certain order. If you lock table A and table B first, lock them in this order in all stored procedures. If you first lock table B in A stored procedure and then lock Table A, this may lead to A deadlock. If the lock sequence is not designed in detail in advance, it is difficult to find deadlocks.
　　
46. Monitor the load of the corresponding hardware through SQL Server Performance Monitor Memory: Page Faults/sec counters. If this value increases occasionally, it indicates that there were threads competing for Memory. If it continues high, memory may be the bottleneck.
Process:
　　
1.% DPC Time indicates the percentage of the processor used to receive and provide services during the sample interval in the deferred program call (DPC. (DPC is running at a lower priority interval than the standard interval ). Because DPC is executed in privileged mode, the percentage of DPC time is part of the privileged time percentage. These times are calculated separately and are not part of the total number of interval computations. This total number shows the average busy hours as the percentage of instance time.
　　
2. If the value of % ProcessorTime counter exceeds 95%, the bottleneck is the CPU. You can consider adding a processor or changing a faster processor.
　　
3.% Privileged Time indicates the percentage of idle processor Time used in Privileged mode. (Privileged mode is a processing mode designed for operating system components and operating hardware drivers. It allows direct access to hardware and all memory. Another mode is the user mode. It is a finite processing mode designed for applications, Environment subsystems, and integer subsystems. The operating system converts the application thread to the privileged mode to access the Operating System Service ). The privileged time % includes the time when the service is interrupted and the DPC is provided. The high privileged time ratio may be caused by a large number of failed device intervals. This counter displays the average busy hours as part of the sample time.
　　
4.% User Time indicates CPU-consuming database operations, such as sorting and executing aggregatefunctions. If the value is very high, you can consider increasing the index and try to reduce the value by using simple table join and horizontal table segmentation methods. PhysicalDisk: Curretn Disk Queue Length counter this value should not exceed 1.5 ~ 2 times. To improve performance, you can add disks. SQLServer: Cache Hit Ratio counter. The higher the value, the better. If the duration is lower than 80%, consider increasing the memory. Note that the value of this parameter is accumulated after being started from SQLServer. Therefore, after running for a period of time, this value cannot reflect the current value of the system.
　　
47. Analyze select emp_name form employee where salary> 3000 in this statement, if salary is of the Float type, the optimizer optimizes it to Convert (float, 3000 ), because 3000 is an integer, we should use 3000.0 during programming, instead of waiting for the DBMS to convert at runtime. Conversion of the same character and integer data.
　　
48. query Association and write order
　　
Select a. personMemberID, * from chineseresume a, personmember bwhere personMemberID = B. referenceid and a. personMemberID = 'jcnprh1_1 '(A = B, B = 'number ')
　　
Select. personMemberID, * from chineseresume a, personmember bwhere. personMemberID = B. referenceid and. personMemberID = 'jcnprh1_1 'and B. referenceid = 'cnprh00001' (A = B, B = 'number', A = 'number ')
　　
Select a. personMemberID, * from chineseresume a, personmember bwhere B. referenceid = 'jcnprh1_1 'and a. personMemberID = 'jcnprh1_1' (B = 'number', A = 'number ')
　　
49,
　　
(1) IF no owner code is entered, THEN code1 = 0 code2 = 9999 ELSE code1 = code2 = owner code end if the SQL statement executed is: Select owner name FROM P2000 Where owner code> =: code1 AND owner code <=: code2
　　
(2) IF no owner code is entered, THEN Select owner name FROM P2000 ELSE code = owner code Select owner code FROM P2000 Where owner code =: the first method of code end if only uses one SQL statement, and the second method uses two SQL statements. When no owner code is entered, the second method is obviously more efficient than the first method because it has no restrictions. When the owner code is entered, the second method is still more efficient than the first method. It not only lacks one restriction condition, but also is the fastest query operation because of equality. Do not worry about writing programs.
　　
50. The new method for querying pages in JOBCN is as follows: Use the performance optimizer to analyze performance bottlenecks. If I/O or network speed is used, the following method is effective. It is better to use the current method on the CPU or memory. Please differentiate the following methods, indicating that the smaller the index, the better.
　　
Begin
　　
DECLARE @ local_variable table (FID int identity (1, 1), ReferenceIDvarchar (20 ))
　　
Insert into @ local_variable (ReferenceID)
　　
Select top 100000 ReferenceID from chineseresume order byReferenceID
　　
Select * from @ local_variable where Fid> 40 andfid <= 60
　　
End and
　　
Begin
　　
DECLARE @ local_variable table (FID int identity (1, 1), ReferenceIDvarchar (20 ))
　　
Insert into @ local_variable (ReferenceID)
　　
Select top 100000 ReferenceID from chineseresume order byupdatedate
　　
Select * from @ local_variable where Fid> 40 andfid <= 60
　　
End
　　
Begin
　　
Create table # temp (FID int identity (1, 1), ReferenceIDvarchar (20 ))
　　
Insert into # temp (ReferenceID)
　　
Select top 100000 ReferenceID from chineseresume order byupdatedate
　　
Select * from # temp where Fid> 40 and fid <= 60 drop table # temp
　　
End

Appendix: storage process writing experience and optimization measures From: Web Teaching Network

1. Suitable for readers: database developers, who have a large amount of data in the database and who are interested in optimizing the SP (stored procedure.

II. Introduction: complex business logic and database operations are often encountered during database development. In this case, SP is used to encapsulate database operations. If there are many SP projects and there is no certain specification for writing, it will affect the difficulties of system maintenance and the difficulty of understanding the big SP logic in the future, in addition, if the database has a large amount of data or the project has high performance requirements for the SP, you will encounter optimization problems. Otherwise, the speed may be slow. After hands-on experience, an Optimized SP is hundreds of times more efficient than an optimized SP with poor performance.

Iii. content:

1. If developers use tables or views of other databases, they must create a View in the current database to perform cross-database operations. It is best not to directly use "databse. dbo. table_name ", because sp_depends cannot display the cross-database table or view used by the SP, it is not convenient to verify.

2. Before submitting the SP, the developer must have used set showplanon to analyze the query plan and perform its own query optimization check.

3. High program running efficiency and application optimization. Pay attention to the following points during SP writing:

A) SQL usage specifications:

I. Avoid large transaction operations as much as possible. Use the holdlock clause with caution to improve the system concurrency capability.

Ii. Try to avoid repeated accesses to the same or several tables, especially tables with large data volumes. You can consider extracting data to a temporary table based on the conditions and then connecting it.

Iii. avoid using a cursor whenever possible because the cursor is inefficient. If the cursor operation contains more than 10 thousand rows of data, it should be rewritten. If the cursor is used, try to avoid table join operations in the cursor loop.

Iv. note that when writing where statements, the order of statements must be taken into account. The order before and after condition clauses should be determined based on the index order and range size, and the field order should be consistent with the index order as much as possible, the range is from large to small.

V. do not perform functions, arithmetic operations, or other expression operations on the left side of "=" in the where clause. Otherwise, the system may not be able to correctly use the index.

Vi. Use exists instead of selectcount (1) to determine whether a record exists. The count function is used only when all the rows in the statistical table are used, and count (1) is more efficient than count.

Vii. Try to use "> =" instead of "> ".

Viii. Note the replacement between the or clause and the union clause.

Ix. Pay attention to the data types connected between tables to avoid the connection between different types of data.

X. Pay attention to the relationship between parameters and data types in stored procedures.

Xi. Pay attention to the data volume of insert and update operations to prevent conflicts with other applications. If the data volume exceeds 200 data pages (400 Kb), the system will update the lock and the page lock will be upgraded to the table lock.

B) Specification for indexing:

I. You should consider creating indexes in combination with applications. We recommend that you create a large OLTP table with no more than six indexes.

Ii. Try to use the index field as the query condition, especially the clustered index. If necessary, you can use indexindex_name to forcibly specify the index.

Iii. Avoid tablescan when querying large tables. If necessary, create an index.

Iv. when using an index field as a condition, if the index is a joint index, you must use the first field in the index as the condition to ensure that the system uses the index, otherwise, the index will not be used.

V. Pay attention to index maintenance, rebuild indexes periodically, and recompile the stored procedure.

C) use of tempdb:

I. Try to avoid using distinct, order by, groupby, having, join, and cumpute, because these statements will increase the burden on tempdb.

Ii. Avoid frequent creation and deletion of temporary tables and reduce the consumption of system table resources.

Iii. when creating a temporary table, if a large amount of data is inserted at one time, you can use select into to replace createtable to avoid logs and increase the speed. If the data volume is small, in order to ease the system table resources, we recommend that you first create a table and then insert it.

Iv. if the temporary table has a large amount of data and requires an index, you should place the process of creating a temporary table and creating an index in a single sub-storage process, in this way, the system can use the index of the temporary table.

V. if a temporary table is used, you must explicitly delete all the temporary tables at the end of the stored procedure. truncate the table first and then droptable, so that the system table can be locked for a long time.

Vi. Use caution when connecting large temporary tables to other large tables to query and modify them, reducing the burden on the system table, because this operation will use the tempdb system table multiple times in one statement.

D) Reasonable algorithm usage:

Based on the SQL optimization technology mentioned above and the SQL Optimization content in the ASETuning manual, combined with practical applications, a variety of algorithms are used for comparison to obtain the method with the least resource consumption and the highest efficiency. Specific ASE optimization commands are available: setstatistics io on, set statistics time on, set showplan on, and so on.

Last article

Replace not in with other statements, such as tables a and B with the same structure. If the data volume is large, replace select * from a where a. c not in (select c from B)

The statement has

A) select a. * from a, B where a. c = B. c + and B. c is null (it is said that the speed is 30 times faster than the original method)

B) select * from a minus select a. * from a, B where a. c = B. c (second speed)

C) select * from a where not exist (select a. * from a, B where a. c = B. c) (also good)