I need a separate table to describe nvarchar (max)

In one of my previous works, we had a separate table in which long descriptions were stored in a text type column. I think this was done due to text type restrictions.

Im now designing tables for an existing application I'm working on, and this question comes to my mind. I resonate with storing a long description of my elements in a single element table in the varchar (max) column. I understand that I cannot index this column, but this is normal since I will not search on these columns.

So far, I see no reason to separate this column from another table.

Could you give me some information if I am missing something or if storing my descriptions in one table on varchar (max) is a good approach? Thanks!

+3
source share
2 answers

, . SQL Server 2005, . TEXT, NTEXT IMAGE . MAX . SQL 2005 3 : , LOB . MAX LOB, . , , , "" .

. .

+5

, , , . , SQL, "" sql .

, varcharmax() , - , .

+1

Source: https://habr.com/ru/post/1717458/


All Articles