Hey men and gals, I've got a area inside a table that I'll be storing different types of data inside it, Like: X-Large, Medium, Small....or I would store: 22-March-2009, 12 months, 24 months, three years...or 06Months, 12 Several weeks, 12 months, or I would store: "33-36", "37-40"...which information is not fixed, i would need later on to include new groups...

The apparent selection of an information type could be an nvarchar(length), but every other suggestions? it is possible to approach to take for this??? thanks inside a advance...

Seems like you are attempting to store a "size". Maybe you'll need a "Size" table with individuals values inside it (X-Large, Medium, Small, 12 months, etc.) as well as an ID area that gets into another table.

The reason why you would should also store to start dating ? within the same area is a little confusing in my experience. Are you certain you should not have two different fields there?

ETA: According to your comment, I recommend developing a couple additional tables:

SizeType - Would define the kind of "size" you had been dealing with (e.g. kids clothing, kids footwear, mens footwear, womens footwear, mens t shirts, mens pants, womens t shirts, womens pants, etc.). Might have two posts - an ID along with a Description.

Size - Would define the person dimensions (e.g. "Size 5", XL, 33-34, -6 Several weeks, etc.). Might have three posts - and ID, an account, and also the corresponding SizeType id from SizeType.

Now in your product table, you'd place the ID in the size table. This provides you some versatility when it comes to adding new dimensions, determining which dimensions opt for which kind of items, etc. You can break it lower further too to create the look better still, but I'd rather not overcomplicate things here.

Regardless of what you need to do, such database design doesn't look great.

Still, you should use BLOB data type to simply store data inside a column, or perhaps a Text type if it is text (by doing this search is more efficient, understanding lower and upper situation and the like).

nvarchar(max) works. Otherwise, you may have multiple posts, among each possible type. That will prevent you from transforming such things as double-precision amounts into strings and back.

  • nvarchar(max) when the information is limited to strings of under 2Gb.
  • ntext if you want to permit strings in excess of 2Gb.
  • binary or image if you want to store binary data.