Is there a drawback when choosing ntext as the data type for all text columns?

Question

Possible duplicate:
Are there any disadvantages to using nvarchar (MAX)?

Is there a common flaw when instead of a type containing characters, but with a limited maximum size, such as 'char' or 'varchar', instead of a type of type ntext, a column type is used?

I'm not sure if the limited column size applies to all of my columns. Therefore, I would use "ntext" for all columns containing text. Could this lead to problems in the future?

(I use Linq-To-SQL in an ASP.NET Webforms application)

Answer 1

NTEXT , NVARCHAR (MAX).

. 4000 , NVARCHAR (MAX). 4000 , NVARCHAR (n).

, NTEXT , . NVARCHAR (MAX) , . , SQL Server . . MSDN.

Edit:
NVARCHAR 4000. MAX, 2 ^ 31-1 .
VARCHAR 8000, MAX.

Answer 2

, AdaTheDev, T-SQL NTEXT. VARCHAR (MAX) NVARCHAR (MAX).

Answer 3

NVARCHAR, , , . .

, NVARCHAR, , VARCHAR, .

, , , VARCHAR.

and, like other answers, do not use TEXT / NTEXT at all, they are deprecated.

Answer 4

You can never have an index in any text column, because the index is limited to 900 bytes.

And ntext cannot be indexed in any way, but there are still restrictions on the new BLOB types.

Do you plan to have only unique text columns? Or are you never planning on looking for them?