Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Altering column from varchar(2048) to varchar(max) performance Expand / Collapse
Author
Message
Posted Wednesday, July 29, 2009 12:25 PM


SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Tuesday, July 22, 2014 6:44 AM
Points: 81, Visits: 369
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
Post #761866
Posted Wednesday, July 29, 2009 1:16 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Wednesday, July 23, 2014 12:40 AM
Points: 7,001, Visits: 8,439
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


Don't drive faster than your guardian angel can fly ...
but keeping both feet on the ground won't get you anywhere

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


- 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
Post #761922
Posted Wednesday, July 29, 2009 4:24 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: General Forum Members
Last Login: Today @ 11:28 AM
Points: 36,786, Visits: 31,244
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."

(play on words) "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T." --22 Aug 2013

Helpful Links:
How to post code problems
How to post performance problems
Post #762019
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse