>Nvarchar uses as many chars as enetered.
>Char uses as many chars as defined in table design.
>Text field uses different place for storage (If I remember well).
>
>So, NVARCHAR is good when you have to store text with very different lengths. This is good for disk space and for better paging of the DB.
>CHAR is better when you have to store a text with almost the same length. That improve speed.

Also, one has to keep in mind that Char is indexable and doesn't require full text indexing to be optimized. IAC, full text indexing will never be as powerful as a regular index, when comes time to search for everything starting with.

>Text I dodn't event want to comment :-). That is like MEMO field in VFP.
>I'm not sure if this type still exists in SQL Server 2012.
>MS warned that "ntext, text, and image data types will be removed in a future version of Microsoft SQL Server".

Yes, but only a small adjustment in the database when time will come.

Thanks for the feedback