词语大全 table lock中文翻譯

Posted 2022-08-15 操作

篇首语：愿君学长松，慎勿作桃李。本文由小常识网(cha138.com)小编为大家整理，主要介绍了词语大全 table lock中文翻譯相关的知识，希望对你有一定的参考价值。

词语大全 table lock中文翻譯

This option only requires an intent - shared table lock
用戶必須是表所有者，或者是

It must acquire a shared table lock
運行dbcc checktable ，則必須獲取一個共享表鎖。

Similarly , page locks are always escalated to table locks
同樣，頁鎖始終升級到表鎖。

Are tables locked during snapshot generation
快照生成期間是否鎖定表？

Table locks are appped for the duration of the index operation
在索引操作期間應用表鎖。

Long - term table locks are not held for the duration of the index operation
在索引操作期間不持有長期表鎖。

Long - term table locks are not held
不保留長期表鎖。

If table locking is specified , the default setting for the table set with
使用表級鎖定如果指定了表鎖定，則使用

If table locking is not used , the default uses row - level locks , unless the
如果未使用表鎖定，默認使用行級鎖定，除非

Specifies that row locks are taken when page or table locks are ordinarily taken
指定通常采用頁鎖或表鎖時，采用行鎖。

Table locking behavior
表鎖定行為

Read operations acquire no page or row locks ; only sch - s table locks are acquired
讀取操作不獲取頁鎖或行鎖，只獲取sch - s表鎖。

The following partial transaction shows how to place an exppcit shared table lock on
上放置一個顯式共享表鎖，以及如何讀取索引。

Table locks are appped and the table is unavailable for the duration of the index operation
應用表鎖，該表在索引操作期間不可用。

Exclusive table locks are held only for a very short amount of time during the alteration process
更改過程中，排他表鎖只保留非常短的時間。

The sql server 2005 database engine will not escalate row or page locks to table locks
Sql server 2005數據庫引擎不會將行鎖或頁鎖升級到表鎖。

Sets the locking behavior for a table during a bulk - import operation . table lock on bulk import
選項可以設置大容量導入操作過程中針對表的鎖定行為。

If holdlock is also specified , the shared table lock is held until the end of the transaction
如果同時指定了holdlock ，那么，在事務結束之前將一直保持該共享表鎖。

Causes dbcc checktable to obtain a shared table lock instead of using an internal database snapshot
可使dbcc checktable獲得一個共享表鎖，而不使用內部數據庫快照。

Table locking can improve performance of the bulk - import operation by reducing lock contention on the table
表鎖定可以通過減少表中的鎖爭用來提高大容量導入操作的性能。

When you specify table locking , a bulk update table - level lock is taken for the duration of the bulk - import operation
指定表鎖定后，在大容量導入操作期間采取大容量更新表級鎖定。

Intent locks , row locks , and page locks all count toward the escalation count , unless they are temporary table locks
除非屬于臨時表鎖，否則意向鎖、行鎖和頁鎖都將計入升級統計中。

The database engine chooses the appropriate lock and can escalate the lock from a row or page lock to a table lock
數據庫引擎將選擇相應的鎖，并且可以將鎖從行鎖或頁鎖升級到表鎖。

Does not perform any allocation checks and must acquire shared table locks to perform table checks
運行dbcc checkfilegroup不會執行任何分配檢查，并且必須獲取共享表鎖才能執行表檢查。

The database engine does not escalate row or key - range locks to page locks , but escalates them directly to table locks
數據庫引擎不會將行鎖或鍵范圍鎖升級到頁鎖，而是將它們直接升級到表鎖。

Does not perform any allocation or catalog checks and must acquire shared table locks to perform table checks
運行dbcc checkdb不會執行任何分配或目錄檢查，并且必須獲取共享表鎖才能執行表檢查。

The dbcc mands use table locks instead of the internal database snapshots when the mand is executed against the following
當針對以下對象執行dbcc命令時，該命令將使用表鎖而不是內部數據庫快照：

Takes page locks either where individual locks are ordinarily taken on rows or keys , or where a single table lock is ordinarily taken
在通常行或鍵采用單個鎖的地方，或者通常采用單個表鎖的地方，請采用頁鎖。

The database engine escalates row or page locks to table locks if the amount of memory used by lock objects exceeds one of the following conditions
如果鎖對象使用的內存量超出下列條件之一，則數據庫引擎將行鎖或頁鎖升級為表鎖：

In this case , an exclusive database lock is required to perform the allocation checks , and shared table locks are required to perform the table checks
在這種情況下，需要排他數據庫鎖才能執行分配檢查，需要共享表鎖才能執行表檢查。

If a snapshot cannot be created , or tablock is specified , dbcc checktable acquires a shared table lock to obtain the required consistency
如果無法創建快照，或指定了tablock ，則dbcc checktable將獲取一個共享表鎖來獲得所需的一致性。

This means long - term blocking table locks are not held and queries or updates to the underlying table can continue during the alter index reorganize transaction
這意味著不保留長期阻塞的表鎖，且對基礎表的查詢或更新可以在alter index reorganize事務處理期間繼續。

Microsoft sql server 2005 mobile edition sql server mobile automatically escalates row locks and page locks into table locks when a transaction exceeds its escalation threshold
當事務超出其升級閾值時， microsoft sql server 2005 mobile edition ( sql server mobile )會自動將行鎖和頁鎖升級為表鎖。

If a transaction acquires a large number of row or page locks , the database engine may grant a table lock and then free all the lower - level locks to minimize locking overhead
如果一個事務獲取了大量的行鎖或頁鎖，則數據庫引擎可能授予它一個表鎖，然后釋放所有較低級別的鎖，以將鎖定開銷降到最小。

If the lock escalation attempt succeeds and the full table lock is acquired , then all heap or b - tree , page page , key - range , or row - level locks held by the transaction on the heap or index are released
如果鎖升級嘗試成功并獲取全表鎖，將釋放事務在堆或索引上所持有的所有堆或b樹鎖、頁鎖（ page鎖）、鍵范圍鎖（ key鎖）或行級鎖（ rid鎖）。

Shared locks acquired for read mitted or repeatable read are generally row locks , although the row locks can be escalated to page or table locks if a significant number of the rows in a page or table are referenced by the read
針對read mitted或repeatable read獲取的共享鎖通常為行鎖，盡管當讀取引用了頁或表中大量的行時，行鎖可以升級為頁鎖或表鎖。