外文翻譯--關于數(shù)據(jù)庫死鎖的知識-數(shù)據(jù)庫(存儲版)
【正文】 ect, looking for solutions. From the above analysis can see, SQL Server database lock is a doubleedged sword. The security database data consistency at the same time, they will give the database caused some negative effect. How do these negative influence to the least, is our database administrators task. In application design, follow the advice above, can effectively solve the problems for the lock blockages, improve the performance of the database. Visible, to basically solve congestion problem, need database management personnel and program developers work together. 中文 關于數(shù)據(jù)庫死鎖的知識 數(shù)據(jù)庫本身提供了鎖管理機制 ,但是從一方面 ,數(shù)據(jù)庫客戶端應用程序的“傀儡” ,這主要是由于客戶端到服務器的完全控制獲得的鎖的 能力。s request, so, the backend database involved in the table, all have been added L locked. So even if the user cancel after inquires, all in the affairs for the locks within will remain. At this point, if other users need to check on the table or the user to open the window through input inquires to query conditions to improve the system response speed occurs when the jam phenomenon. Second, the client not to get all the results of my query. Usually, the user will be sent to the server after queries, foreground application must be done at once extraction all the results do. If the application did not extract all the results trip, it produces a problem. For as long as the application did not withdraw promptly all the results, the lock may stay at table and block other users. Since the application has been submitted to the server will SQ statements, the application must be extracted all results do. If the application does not follow the principle words (such as because at that time and no oversight configuration), can39。t have a puter so fast. So, during the implementation of the user participation to let the process, will extend the affairs of waiting time. So unless there is a special needs, not in the application39。如果用戶打開窗戶口查詢之后 ,因為用戶發(fā)現(xiàn)反映緩慢崩潰或被迫取消查詢。如果應用程序沒有遵循原 則詞 (比如因為在那個時候 ,沒有監(jiān)督配置 ),不能從根本上解決擁堵。 通常 ,為了避免沖突的擁塞在鎖上 ,作者提出以下的建議。同時 ,在應用程序級別設置合理的緩存 ,也可以是非常顯著提高查詢效率。一些事務的執(zhí)行必須參數(shù) ,最好事先提供。 如果通過改變事務的時間較長。但是 ,通常 ,可以有效地避免擁塞的發(fā)生 ,提高數(shù)據(jù)庫的性能。這兩方面聯(lián)系在一起 ,可能導致應用程序提高運行的時間過程查詢。在沒有之前再提問 ,因為他們的應用程序就能實現(xiàn)緩存數(shù)據(jù) ,所以不僅僅是更新的內容。用戶可以查詢過程點擊該按鈕取消瀏覽。當數(shù)據(jù)庫管理員發(fā)現(xiàn) ,阻斷這些癥狀 ,能從這些方面 ,尋找解決方案。 。這也是數(shù)據(jù)庫管理員需要規(guī)劃發(fā)展問題的談判。在這段時間 ,他們會想到取消 ,問。 同時 ,可以在列表框設計“搜索”功能。一方面 ,自然的孩子 ,將查詢速度緩慢 。所以每一類更新公司的消費時間可能會極大地降低。 如果數(shù)據(jù)庫產品信息表 ,它記錄編號二百萬。因此 ,在實現(xiàn)用戶的參與讓這個過程中 ,將擴展事務的等待時間。 因此 ,筆者建議在應用程序設計、數(shù)據(jù)庫查詢記錄來提取時間。 所以通常 ,不要把長時間運行決策支持搜索和在線事務處理 ,詢問混合在一起。只要應用程序沒有及時提取所有的結果 ,鎖可能呆在桌子和阻止其他用戶。 大多數(shù)應用程
畢業(yè)設計相關推薦
鄂ICP備17016276號-1