Watch the 7.3 Webinar On-Demand
This new release brings updates to Universal Storage, query
optimization, and usability that you won’t want to miss.
Certain operations will take either a database lock or a cluster lock. This topic explains what these locks are, their impact, and the operations that use them.
a
takes a shared lock to perform CREATE DATABASE
. Database b
takes a shared lock to perform BACKUP DATABASE
concurrently.ADD LEAF
is running on the cluster. While the operation is running, CREATE TABLE
tries to run, but is blocked until ADD LEAF
completes.The following operations take database locks:
ALTER DATABASE
ALTER TABLE
ALTER VIEW
BACKUP DATABASE
CREATE DATABASE
CREATE INDEX
CREATE VIEW
DROP DATABASE
DROP INDEX
DROP VIEW
REBALANCE PARTITIONS
RESTORE DATABASE
RESTORE REDUNDANCY
OPTIMIZE TABLE
(for rowstore tables only)TRUNCATE
The following operations take cluster locks:
ADD AGGREGATOR
ADD LEAF
AGGREGATOR SET AS MASTER
ATTACH LEAF
ATTACH LEAF ALL
BOOTSTRAP AGGREGATOR
CHECK BLOB CHECKSUM
CLEAR ORPHAN DATABASES
CONTINUE REPLICATING
DETACH LEAF
PAUSE REPLICATING
REBALANCE ALL DATABASES
REMOVE AGGREGATOR
REMOVE LEAF
REPLICATE DATABASE
STOP REPLICATING