分布式数据库死锁检测算法主要分为集中式、层次式和分布式。
Deadlock detection algorithms of distributed database can be classified into centralized, layered and distributed.
根据分布式数据库中事务发出不同的资源请求方式，现有的分布式数据库死锁检测算法通常针对某种资源请求模型而提出。
According to different resource request that issued by transactions, existing deadlock detection algorithms of distributed database are commonly presented for certain resource request model.
如果两个方法都试图访问同一张表，您就可能遇到来自数据库的死锁。
You may experience deadlocks from a database if both methods try to access to the same table.
否则，数据库引擎会把身份验证请求路由到插件，这会在处理前一个身份验证请求期间形成死锁。
An authentication request would be routed by the database engine to the plug-in, which would cause a deadlock during the processing of the previous authentication request.
这使得数据库系统管理员可以优化没有使用更新语句处的性能，或使用更新语句时也可以防止死锁。
This allows the database administrator to optimize the performance where the update syntax is not used, or to prevent deadlocks when it is used.
数据库识别出死锁事件。
带有语句历史功能的死锁事件监视器适用于所有应用程序，会增加DB 2数据库管理程序对监视器堆的大量使用。
A deadlock event monitor with statement history capabilities affects all applications and increases the monitor heap usage by the DB2 database manager.
在任何数据库环境中，死锁检测对于应用程序并发性都是很重要的。
Deadlock detection is important in any database environment for application concurrency.
收集整个数据库的死锁事件数据。
运行多个DB 2 MOVE命令将模式从一个数据库复制到另一个数据库会导致死锁。
Running multiple DB2MOVE commands to copy schemas from one database to another results in deadlocks.
数据库的激活将启动日志记录器来记录活动以及启动死锁检测器来检测死锁。
Activating a database starts the logger for logging activity and the deadlock detector for detecting the deadlocks.
当使用JBossCache 1 .x，我们在从数据库读取数据并将其放到JBossCache区域中，有时会遇到性能问题，甚至还会发生死锁。
With JBossCache 1.x we would run into performance and sometimes even deadlock issues when reading data from the database and putting that into the JBossCache region.
MDMServer环境中事件监控器的一个常见用途是死锁事件监控，用于了解和解决 MDM Server 数据库中偶尔发生的过度死锁（excessive deadlocks）。
One common usage of event monitor in the MDM Server environment is deadlock event monitoring to understand and resolve excessive deadlocks that sometimes happen in an MDM Server database.
本文将详细介绍分布式事务、并发控制和资源请求模型，总结出分布式数据库系统的通用死锁条件。
In this paper, distirbuted transaction, concurrency control and resource request model are introduced in detail. The universal deadlock condition in distirbuted database system is summarized.
通常，数据库引擎仅定期执行死锁检测。
The Database Engine typically performs periodic deadlock detection only.
上面列出的所有资源均参与数据库引擎死锁检测方案。
All of the resources listed in the section above participate in the Database Engine deadlock detection scheme.
数据库系统中事务死锁的检测和预防，对提高系统并发性和整体性能具有重要意义。
Deadlock detection and prevention of transaction are very important to concurrency and integrity in database systems.
如何有效的解决数据库中并发控制带来的死锁现象，就此提出了几个解决途径和遵循原则。
How to organize and store data scientificaly and how to solve the deadlock of parallel control, this paper puts forward several methods.
分布式数据库不同于一般分布式系统，其死锁条件不仅与资源请求方式相关，而且与资源授予方式相关。
Distributed database is different from general distributed system, it's deadlock condition is not only related with resource request mode, but also related with resource grant mode.
数据库的并发控制，经常导致死锁，本文针对此问题给出检测方法。
Concurrency control in database always leads to deadlock. This article has put forward a method to detect it.
数据库的并发控制，经常导致死锁，本文针对此问题给出检测方法。
Concurrency control in database always leads to deadlock. This article has put forward a method to detect it.
应用推荐