Altering column from varchar(2048) to varchar(max) performance

• Mike Byrd

  Default port

  Points: 1458

  More actions

  July 29, 2009 at 12:25 pm

  #134341

  If I run following TSQL (original column defined as VARCHAR(2048)

  ALTER TABLE dbo.SystemLog

  ALTER COLUMN LogData VARCHAR(MAX);

  It takes ~75 minutes to complete, but if I run (original column defined as VARCHAR(2048)

  ALTER TABLE dbo.SystemLog

  ALTER COLUMN LogData VARCHAR(8000);

  It only takes 2 seconds to complete (refreshed copy of original table).

  Can anybody tell me why the conversion from VARCHAR(2048) to VARCHAR(MAX) takes so long. It was my understanding that data within a varchar(max) column was retained in the table data if it fit within the page, but if not, then moved elsewhere like the deprecated TEXT field was. Obviously something is going on.

  Any ideas please? Thanks in advance.

  Mike Byrd

• Johan Bijnens

  SSC Guru

  Points: 135255

  More actions

  July 29, 2009 at 1:16 pm

  #1031985

  altering to varchar(8000) is only a catalog operation (and maybe an index op if the column is indexed) because it stays the same datatype, only the var length changes.

  Changing to datatype varchar(max) is actually a change to an other datatype ! (max characteristics)

  Johan
  
  Learn to play, play to learn !

  Dont drive faster than your guardian angel can fly ...
  but keeping both feet on the ground wont get you anywhere :w00t:

  - How to post Performance Problems
  - How to post data/code to get the best help[/url]

  - How to prevent a sore throat after hours of presenting ppt

  press F1 for solution, press shift+F1 for urgent solution 😀

  Need a bit of Powershell? How about this

  Who am I ? Sometimes this is me but most of the time this is me

• Jeff Moden

  SSC Guru

  Points: 1003853

  More actions

  July 29, 2009 at 4:24 pm

  #1032063

  ALZDBA (7/29/2009)

  ---

  altering to varchar(8000) is only a catalog operation (and maybe an index op if the column is indexed) because it stays the same datatype, only the var length changes.

  Changing to datatype varchar(max) is actually a change to an other datatype ! (max characteristics)

  This also drives the data to an "out of row" condition. It has to find a reference and then go outside the row and page to find the data. All of that takes extra time.

  --Jeff Moden

  ---

  RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
  First step towards the paradigm shift of writing Set Based code:
  ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

  Change is inevitable... Change for the better is not.
  

  ---

  Helpful Links:
  How to post code problems
  How to Post Performance Problems
  Create a Tally Function (fnTally)