This is not necessarily a feature request, however I didn't know where to ask about this. In the MSDN, there is a note I just read while I happened to be looking for something else. It is found here: http://msdn.microsoft.com/en-us/library/ms187993.aspx
It states this -
ntext, text, and image (Transact-SQL)
SQL Server 2008 R2
"Important
ntext, text, and image data types will be removed in a future version of Microsoft SQL Server. Avoid using these data types in new development work, and plan to modify applications that currently use them. Use nvarchar(max), varchar(max), and varbinary(max) instead.
Fixed and variable-length data types for storing large non-Unicode and Unicode string and binary data. Unicode data uses the UNICODE UCS-2 character set."
My question is - will this be supported in future releases of the CMS? I assume it will be, but I just wanted to make sure the staff at EPiServer was aware of this.
This is not necessarily a feature request, however I didn't know where to ask about this. In the MSDN, there is a note I just read while I happened to be looking for something else. It is found here: http://msdn.microsoft.com/en-us/library/ms187993.aspx
It states this -
ntext, text, and image (Transact-SQL)
"
Important
ntext, text, and image data types will be removed in a future version of Microsoft SQL Server. Avoid using these data types in new development work, and plan to modify applications that currently use them. Use nvarchar(max), varchar(max), and varbinary(max) instead.
Fixed and variable-length data types for storing large non-Unicode and Unicode string and binary data. Unicode data uses the UNICODE UCS-2 character set."
My question is - will this be supported in future releases of the CMS? I assume it will be, but I just wanted to make sure the staff at EPiServer was aware of this.
Best,
Christine