New answers tagged

0

There are good reasons ALGORITHM=INPLACE may not be used and switches to ALGORITHM=COPY. REASON #1 In the link you gave in the question, there is a chart that shows the following: Adding a FULLTEXT index trigger a table copy is not supported for online operation Many operations can revert to copy because it says in the notes Although ALGORITHM=INPLACE is ...


5

Assuming we're talking about a plain ALTER TABLE, not an operation done through some wizard that does temp table and rename tricks or anything similar. A straight column data type change may result in update of every row in the table. It depends on the types involved. You have to consider this: the row image in the table is just a bag of bytes, until is ...


2

I am quoting a paragraph Appendix A: Using Management Studio to Change Data Types from SQL Server 2005 document on Impact Of Changing Collation and Data types When you change data type of column following things happen Internally, SQL Server creates a temporary table that has the same column property as that in the target column. Next an ...


3

I believe that the db engine is creating a new temporary table and filling it. Looking at your execution plan might provide clues. You can see the quote in the following article but after searching I did not see anything official in MS documentation. Also, if you are running this using SSMS designer it may have different behavior than executing the ...



Top 50 recent answers are included