Microsoftbut there are still situations where such schema changes can have a direct and negative impact on production workloads.
I'd like to know more about these situations but am not very familiar with SQL Server. Could you elaborate on the situations in which schema changes can have negative impacts on production workloads?
MicrosoftWe have introduced online operations such as index create, rebuild or drop and alter column, but these are not supported in all versions of SQL Server (i.e. not Enterprise Edition) and have some other caveats (i.e. is there a legacy LOB column etc.) and they tend to use more disk space and CPU than offline operations. There are also other restrictions that force operations to be done offline (i.e. change a column that is part of a PK or FK). HTH
