例如，锁快照捕获并返回数据库锁信息。
For example, a lock snapshot captures and returns database lock information.
事务锁(数据库锁)是单个事务工作单元内出现的锁。
Transaction locks (database locks) are those that occur within a single transactional unit of work.
是否明年触发器内发生火灾，应明确数据库锁的收购。
Whether or not the acquisition of next triggers to fire should occur within an explicit database lock.
要支持高数据库并发性，则需要减少数据库锁，并尽可能缩短保持资源的时间。
To support high database concurrency, you need to reduce database locks and hold resources for as little time as possible.
在手动删除数据库锁文件之前，请务必确认在数据库机器上没有JVM在运行。
Be sure to verify that no JVMs are running on the database machine before manually removing a database lock file.
当映射常规也的时候，OS按需求，并且会请求工作集锁和PF N数据库锁。
When mapping regular pages, OS does it on demand and hence will have to acquire both working set and PFN database lock for every page.
现在我们已经准备就绪，可以从newstaff表导出数据，并同步捕获数据库锁快照了。
We are now ready to export the data from the NEWSTAFF table, and to simultaneously capture a database lock snapshot.
该数据库管理员必须完成孤立的事务分支，以释放这些事务分支所持有的数据库锁。
The database administrator might have to complete the orphaned transaction branches for releasing the database locks that they hold. For the database administrator, this is a two step process.
当数据库没有被正确关闭(例如，崩溃或中止)时，就会留下一个“孤立的”数据库锁文件。
When a database is not properly shutdown (for example, a crash or an abort) an 'orphan' database lock file will be left.
同乐观锁定策略相比，物理数据库锁需要持续较长的时间，因此应用程序性能和吞吐量很可能会受到影响。
As physical database locks are held for a longer time duration than with an optimistic locking strategy, there is more of a chance for performance and throughput being impacted.
waldo夫人正意外地展示2pc的缺点：需要数据库锁来保证隔离，但这样可能对数据访问(和并发)有负面影响。
Mrs. Waldo is accidentally demonstrating a drawback of 2pc: database locks are needed to guarantee isolation and this can have negative consequences for data access (and concurrency).
第二个属性——只要获取工作集锁和PF N数据库锁一个，可以让应用程序运行的更快并且有更好的扩展性。
The second property - taking both working set and PFN's database lock only ones enables applications to perform faster and better scalable ramp up.
注意2：因为你使用BEGIN而不是BEGINIMMEDIATE数据库锁实际上并不是到的第一个语句的事务了。
Caveat 2: Since you use BEGIN rather than BEGIN IMMEDIATE the database lock is not actually taken until the first statement of the transaction is stepped.
在此方案中，用户从数据库中检索数据而不加任何锁。
In this scenario, a user retrieves data from the database with no locks.
通过这种方法，所有读取操作和相应的处理将在事务的上下文之外执行，因此不会在事务持续时间内在数据库中保持锁。
This way, all of the read operations and corresponding processing execute outside of a transaction's context, and consequently do not hold locks in the database for the duration of the transaction.
只有在事务提交时才需要数据库写入锁，以确保原子地更新已修改的项，而不受到并发更新的干扰。
Database write locks are needed only at transaction commit time to ensure that the modified items are updated atomically without interference from concurrent updaters.
但是，获取并在数据库中保留锁仅仅是高并发性任务的一个部分。
But obtaining and holding locks in the database is only part of the high-concurrency story.
因为可用的存储空间不是无限制的，DB 2数据库管理器必须限制可用于锁的空间数量。
Because the space available is not infinite, the DB2 database manager must limit the amount of space that can be used for locks.
因此，您数据库中的锁争用将明显降低，并且您的应用程序服务器具有更短且更分散的工作单元，这将降低CPU和JVM的内存开销。
Thus, the lock contention is significantly reduced in your database, and your application server has shorter and more discrete units of work, which reduces CPU and JVM memory overhead.
通过使用乐观并发控制，数据库管理器在完成读操作之后可以立即释放行或页锁。
With optimistic concurrency control, the database manager releases the row or page locks immediately after a read operation.
并发控制在业务事务术语中通常涉及生成和维护数据存储上的锁，例如关系数据库。
Concurrency control in business transaction terms usually involves generating and maintaining locks on data stores, such as relational databases.
IDS允许应用程序开发人员将锁放在不同的对象上，如数据库、表、页或行、以及索引。
IDS allows application developers to place locks on different objects, like databases, tables, pages or rows, and indexes.
根据创建数据库所使用的数据定义语言 (DDL)模式文件，可以确定正在使用的锁类型。
You can determine the types of locks being used from the Data Definition Language (DDL) schema files used to create the database.
传统的关系数据库管理系统有时使用锁来管理并发性，从而防止其他客户机访问某个客户机正在更新的数据。
Traditional relational database management systems sometimes use locking to manage concurrency, preventing clients from accessing data while another client is updating that data.
使用缺省锁，但是让LOCKLIST和MAXLOCKS数据库配置参数的值比较小。
Use default locking, but have small values for the LOCKLIST and MAXLOCKS database configuration parameters.
无论是锁还是事务都没影响，因为缓存自数据从数据库加载后就不会改变。
Neither locks nor transactions really matter because the cache never changes once it has been loaded from the database.
软锁缓存；在一个事务中更新数据库；在上一个事务成功完成后更新缓存；否则释放软锁。
Softlocks cache; updates database in a transaction; updates cache after the previous transaction has completed successfully; otherwise releases the softlock.
乐观锁是一个极其有效的并发性控制方法，它可以确保数据完整性而又无需在数据库中放置任何物理锁。
Optimistic locking is an extremely efficient concurrency control method that guarantees data integrity without placing any physical lock in the database.
DB 2使用数据库对象上的锁来确保事务的一致性。
DB2 ensures transaction consistency using locks on database objects.
在图7中，DB 2探测到SAMPLE数据库每小时的锁数量大量增加。
In Figure 7, DB2 has detected a large number of lock escalations per hour for the SAMPLE database.
应用推荐