There are little tricks one can do to increase concurrency, but if your applications need table-level or row-level locks, a DBMS will better suit your needs.
虽然有一些增加并发的技巧，但是，如果应用程序需要的是表级别或行级别的锁定，那么DBMS能够更好地满足您的需求。
For MDC tables, the selection of BLOCKINSERT may improve the performance of INSERT operations by locking at the block level and avoiding row locks for INSERT operations.
对于mdc表，选择BLOCKINSERT可以提高INSERT操作的性能，因为使用的是块级的锁，避免了为INSERT操作使用行锁。
These locks could be table level, row level, or lock on index, and so on.
这些锁可以是表级锁、行级锁、索引锁等等。
The stream driver USES row level locks.
流驱动程序将使用低级锁。
In fact, the only row-level locking that remains during INSERT is the next-key locks that are required to protect an INSERT from adding keys to repeatable read scanners.
实际上，在INSERT期间惟一保持的行级锁是next - key锁，这个锁用于使INSERT不会添加键到可重复的读扫描器。
These next key locks are only obtained when the key INSERT finds that a scanner with a Repeatable Read (RR) isolation level has a row lock on the next-higher key in the index.
这些nextkey锁只有在keyINSERT发现带有RepeatableRead (RR)隔离级别的扫描器在索引中的next -higher键上有一个行锁时才能获得。
Release the row locks so that other applications can SELECT, INSERT, UPDATE, and DELETE from the table (for example, use isolation level cursor stability or uncommitted read).
释放行锁，以便其他应用程序可以对表执行SELECT、INSERT、UPDATE和DELETE(例如，使用游标稳定性(curs or stability)隔离级别或未提交读(uncommitted read)隔离级别)。
So we can see 3 active locks: exclusive lock on key (row) level and 2 intent-exclusive locks on the page and table levels.
我们看到了3个锁信息，一个排它锁在行记录上，两个意向排它锁在页级以及数据表对象上。
So we can see 3 active locks: exclusive lock on key (row) level and 2 intent-exclusive locks on the page and table levels.
我们看到了3个锁信息，一个排它锁在行记录上，两个意向排它锁在页级以及数据表对象上。
应用推荐