2 Removing = Dropping!
source | link

I have some questions regarding the (still deprecated) (N)TEXT datatype in Sql Server - in many tables I can find (N)TEXT columns and many (90%+) rows where those values are NULL, so their use case seems to be obsolete and removing(DROPPING!) them is an option - but the benefits have to be weighted in comparison to the effort in app code.

  1. Will query performance improve at all in case (N)TEXT columns are removed from tables in genereal (let's assume the column is not explicitely part of the query output and there is a nonclustered index covering the query)?

  2. Will query performance especially for "SELECT *" - queries be improved by removing them?

  3. Does removing such a column have any effect on used space in case all rows have a NULL value stored in the (N)TEXT column?

  4. Is any of those improvement depending on wether the content is NULL or NOT NULL?

I have some questions regarding the (still deprecated) (N)TEXT datatype in Sql Server - in many tables I can find (N)TEXT columns and many (90%+) rows where those values are NULL, so their use case seems to be obsolete and removing them is an option - but the benefits have to be weighted in comparison to the effort in app code.

  1. Will query performance improve at all in case (N)TEXT columns are removed from tables in genereal (let's assume the column is not explicitely part of the query output and there is a nonclustered index covering the query)?

  2. Will query performance especially for "SELECT *" - queries be improved by removing them?

  3. Does removing such a column have any effect on used space in case all rows have a NULL value stored in the (N)TEXT column?

  4. Is any of those improvement depending on wether the content is NULL or NOT NULL?

I have some questions regarding the (still deprecated) (N)TEXT datatype in Sql Server - in many tables I can find (N)TEXT columns and many (90%+) rows where those values are NULL, so their use case seems to be obsolete and removing(DROPPING!) them is an option - but the benefits have to be weighted in comparison to the effort in app code.

  1. Will query performance improve at all in case (N)TEXT columns are removed from tables in genereal (let's assume the column is not explicitely part of the query output and there is a nonclustered index covering the query)?

  2. Will query performance especially for "SELECT *" - queries be improved by removing them?

  3. Does removing such a column have any effect on used space in case all rows have a NULL value stored in the (N)TEXT column?

  4. Is any of those improvement depending on wether the content is NULL or NOT NULL?

1
source | link

Will removing NTEXT columns improve performance and reduce space used?

I have some questions regarding the (still deprecated) (N)TEXT datatype in Sql Server - in many tables I can find (N)TEXT columns and many (90%+) rows where those values are NULL, so their use case seems to be obsolete and removing them is an option - but the benefits have to be weighted in comparison to the effort in app code.

  1. Will query performance improve at all in case (N)TEXT columns are removed from tables in genereal (let's assume the column is not explicitely part of the query output and there is a nonclustered index covering the query)?

  2. Will query performance especially for "SELECT *" - queries be improved by removing them?

  3. Does removing such a column have any effect on used space in case all rows have a NULL value stored in the (N)TEXT column?

  4. Is any of those improvement depending on wether the content is NULL or NOT NULL?