【正文】 s. 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. Suggest four: child inquires the and list box, had better not use at the same time. Sometimes in the application of design, through the list box can really improve user input speed and accuracy, but, if foreground application does not have buffer mechanism, you often can cause congestion. As in a order management system, may need frequent input sales representatives. In order to user input convenience, sales representative often design into a list box. Every time need to input, foreground application from the background of all sales representative inquires information (if the application is not involved in the cache). On one hand, the son of nature, would be speed query slow。 三、查詢執(zhí)行時(shí)間過長。 建議二：在事務(wù)執(zhí)行時(shí)不要讓用戶輸入內(nèi)容。 如果涉及到級(jí)聯(lián)更新它 ,時(shí)間會(huì)更長。和其他的用戶查詢 ,例如系統(tǒng)管 理員需要維護(hù)客戶信息 ,充血。同時(shí) ,在按鈕事件 ,需要注意加入一個(gè)回滾命令?？梢?,要從根本上解決擁堵問題 ,需要數(shù)據(jù)庫管理人員和項(xiàng)目開發(fā)人員一起工作。如果用戶查詢所有產(chǎn)品的信息 ,可能會(huì)覺得響應(yīng)時(shí)間長 ,難以忍受。每次需要輸入 ,前臺(tái)應(yīng)用程序從背景的查詢將銷售代表信息 (如果應(yīng)用程序沒有涉及緩存 )。同時(shí) ,它分解成一些簡短的業(yè)務(wù)事務(wù)。當(dāng)別人查詢數(shù)據(jù) ,將發(fā)生阻塞的。如果應(yīng)用程序沒有旅行中提取所有的結(jié)果 ,它就會(huì)產(chǎn)生問題。t take long time running decision support search and online transaction processing inquires the mixed together. When database meet blocked, often need to check the application submitted to the SQL statement 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。