ntext vs nvarchar(max) in SQL 2005

A colleague today told me that using nvarchar(max) in SQL server could be more beneficial than ntext because you can do full text searching and like commands on the field. Technet has this to say: “Variable-length Unicode character data. n can be a value from 1 through 4,000. max indicates that the maximum storage size […]
February 8, 2009 8:50 am

A colleague today told me that using nvarchar(max) in SQL server could be more beneficial than ntext because you can do full text searching and like commands on the field.

Technet has this to say: “Variable-length Unicode character data. n can be a value from 1 through 4,000. max indicates that the maximum storage size is 2^31-1 bytes.”

If I read this correctly it means you can only store 4000 characters, however the storage available is massive. ntext has been deprected, and is therefore not recommended for use in SQL2005. So get this in yer noggin and stop creating new tables with text / ntext to avoid problems later on.

Leave a Comment