外文翻譯--關(guān)于數(shù)據(jù)庫(kù)死鎖的知識(shí)-數(shù)據(jù)庫(kù)(存儲(chǔ)版)
【正文】 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. 中文 關(guān)于數(shù)據(jù)庫(kù)死鎖的知識(shí) 數(shù)據(jù)庫(kù)本身提供了鎖管理機(jī)制 ,但是從一方面 ,數(shù)據(jù)庫(kù)客戶(hù)端應(yīng)用程序的“傀儡” ,這主要是由于客戶(hù)端到服務(wù)器的完全控制獲得的鎖的 能力。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。如果用戶(hù)打開(kāi)窗戶(hù)口查詢(xún)之后 ,因?yàn)橛脩?hù)發(fā)現(xiàn)反映緩慢崩潰或被迫取消查詢(xún)。如果應(yīng)用程序沒(méi)有遵循原 則詞 (比如因?yàn)樵谀莻€(gè)時(shí)候 ,沒(méi)有監(jiān)督配置 ),不能從根本上解決擁堵。 通常 ,為了避免沖突的擁塞在鎖上 ,作者提出以下的建議。同時(shí) ,在應(yīng)用程序級(jí)別設(shè)置合理的緩存 ,也可以是非常顯著提高查詢(xún)效率。一些事務(wù)的執(zhí)行必須參數(shù) ,最好事先提供。 如果通過(guò)改變事務(wù)的時(shí)間較長(zhǎng)。但是 ,通常 ,可以有效地避免擁塞的發(fā)生 ,提高數(shù)據(jù)庫(kù)的性能。這兩方面聯(lián)系在一起 ,可能導(dǎo)致應(yīng)用程序提高運(yùn)行的時(shí)間過(guò)程查詢(xún)。在沒(méi)有之前再提問(wèn) ,因?yàn)樗麄兊膽?yīng)用程序就能實(shí)現(xiàn)緩存數(shù)據(jù) ,所以不僅僅是更新的內(nèi)容。用戶(hù)可以查詢(xún)過(guò)程點(diǎn)擊該按鈕取消瀏覽。當(dāng)數(shù)據(jù)庫(kù)管理員發(fā)現(xiàn) ,阻斷這些癥狀 ,能從這些方面 ,尋找解決方案。 。這也是數(shù)據(jù)庫(kù)管理員需要規(guī)劃發(fā)展問(wèn)題的談判。在這段時(shí)間 ,他們會(huì)想到取消 ,問(wèn)。 同時(shí) ,可以在列表框設(shè)計(jì)“搜索”功能。一方面 ,自然的孩子 ,將查詢(xún)速度緩慢 。所以每一類(lèi)更新公司的消費(fèi)時(shí)間可能會(huì)極大地降低。 如果數(shù)據(jù)庫(kù)產(chǎn)品信息表 ,它記錄編號(hào)二百萬(wàn)。因此 ,在實(shí)現(xiàn)用戶(hù)的參與讓這個(gè)過(guò)程中 ,將擴(kuò)展事務(wù)的等待時(shí)間。 因此 ,筆者建議在應(yīng)用程序設(shè)計(jì)、數(shù)據(jù)庫(kù)查詢(xún)記錄來(lái)提取時(shí)間。 所以通常 ,不要把長(zhǎng)時(shí)間運(yùn)行決策支持搜索和在線(xiàn)事務(wù)處理 ,詢(xún)問(wèn)混合在一起。只要應(yīng)用程序沒(méi)有及時(shí)提取所有的結(jié)果 ,鎖可能呆在桌子和阻止其他用戶(hù)。 大多數(shù)應(yīng)用程
畢業(yè)設(shè)計(jì)相關(guān)推薦
鄂ICP備17016276號(hào)-1