Today I was troubleshooting a nasty exception error on a stock HTML module. It was showing index was out of range/format HTML text error on module load. Turns out, the site content editor was trying to put in binary version of images inline to the HTML, so the module crapped out. We overwrote the content with the previous version and crisis averted. 

That's when I looked into the table structure for dbo.HTMLText and realized that the "Content" column storing all the HTMLs is still using NTEXT as data type. Really? NTEXT was deprecated in SQL 2005 in favor of NVARCHAR(MAX). By design, reading from NTEXT column generally incurs a lot more LOB logical reads than reading from NVARCHAR(MAX), therefore degrading the performance. 

Given that HTML module is used basically everywhere on a DNN website, this seems like an odd choice. Is there a particular reason why we're still stuck with NTEXT?

P.S. We're on DNN Plaftform 7.4.2