Deprecated but Forgotten: Why SQL Server’s Text, NText, and Image Data Types Still Haunt Your Systems

Question

Post reply

Deprecated but Forgotten: Why SQL Server’s Text, NText, and Image Data Types Still Haunt Your Systems

Chandan Shukla

Right there with Babe

Points: 783
More actions
August 6, 2025 at 2:00 pm

#4625341

Comments posted to this topic are about the item Deprecated but Forgotten: Why SQL Server’s Text, NText, and Image Data Types Still Haunt Your Systems

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

Site Owners SSC Guru Points: 80381 More actions · Answer 1

Thanks for posting your issue and hopefully someone will answer soon.

This is an automated bump to increase visibility of your question.

Jeff Moden SSC Guru Points: 1004646 More actions · Answer 2

Nice article.

TBH though, there are a lot of things listed as "disadvantages" for these 3 datatypes that I also wish you couldn't do with the newer MAX datatypes. I also love the fact that they default to out of row instead of in row, like the newer MAX datatypes do. The newer one's create a phenomenon that I called "Trapped Short Rows", which can account for permanent page densities in the low 60s range.

--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)