none
Lock Escalation - What's happening here?

    Question

  • While altering a table (removing a column) in SQL Server 2008, I clicked the Generate Change Script button and I noticed that the change script it generated drops the column, says "go" and then runs an additional ALTER TABLE statement that appears to set the lock escapation for the table to "TABLE". Example:

    ALTER TABLE dbo.Contract SET (LOCK_ESCALATION = TABLE)
    I should also note that this is the last thing the change script is doing. What is it doing here and why is it setting the LOCK_ESCALATION to TABLE?
    Blades Don't Need Reloading...
    Monday, November 09, 2009 8:33 PM

Answers

All replies