My research suggests I can drop a column on a table in a matter of moments (provided I obtain an exclusive lock) because it is only a metadata change.
The table has two different services constantly inserting and updating records. It is very hot. Without developing a full reproduction environment of this level of activity, how can I am asking:ensure a statement like
ALTER TABLE x DROP COLUMN y
will TABLOCKX in my ALTER TABLE x DROP COLUMN y allow this action tosuccessfully obtain an exclusive lock the table, do the drop quickly, and then unlock the table?
How will SQL Server queue this request (eg First In First Out)? Can I be sure the DROP COLUMN will truly only take a few moments?
Locking this table in PROD for an extended time will be unacceptable so I am trying to avoid surprises.
Other notes: Later I will re-index ONLINE to defragment the index and reclaim the space.