【正文】
itself, and check and connection management, all the results do processing and other relevant application behavior. Usually, the lock for to avoid the conflict in the jam, the author has the following Suggestions. Suggest a: after the pletion of the extraction of all query results do. Some applications in order to improve the response speed of the user inquires, will have the option of extraction need record. The smart looks very reasonable, but, but will cause more waste. Because inquires not timely and fruit extraction of words, the lock cannot be released. When others inquires the data, will be happening. So, the author suggest in application design, database query for record to the extraction of in time. Through other means, such as adding inquires the conditions, or the way backstage inquires, to improve the efficiency of the inquires. At the same time, in the application level set reasonable cache, and can also be very significantly improved query efficiency. Suggest two: in the transaction execution don39。t remend the database administrator tend to do so. Because if the user in affairs during the exec ution of the input and number, will extend the affairs of the execution time. Although people smarter, but the response speed still don39。s execution process, reminds the user input parameters. Some affairs of the executive must parameters, best provide beforehand. If can through the variables in the parameters such as need to go in. Suggest three: make affairs as far as possible the brief. The author thinks that, database administrator should put some problem is simplified. When a need to many SQL statements to plete, might as well take the task deposition. At the same time, it breaks down into some brief business affairs. If the database a product information table, its record number two million. Now in a management needs, the onetime change one of the one million five hundred thousand record. If through a change affairs, the time is long. If it involves cascade update it, is time the meeting is longer. In view of this situation, we can learn affairs brief words. If the product information, may have a product type field. So in the update data, can we not onetime updates. But through the product category fields to control, to record the iteration points. So every category of update firm consumption of time may be greatly reduces. So although operation, will need more steps. But, can effectively avoid to go to the occurrence of congestion, and improve the performance of the database.