Why has ASPDNSF opted for use of NText rather than NVarchar(Max) for various fields. IE: Product.Description
Would NVarchar(Max) be better? Any problems in changing this data type?
Why has ASPDNSF opted for use of NText rather than NVarchar(Max) for various fields. IE: Product.Description
Would NVarchar(Max) be better? Any problems in changing this data type?
Technically speaking, the original database was probably designed back in the times of SQL Server 2000, where ntext was the norm. nvarchar only arrived in SQL Server 2005, I think.
You could always try changing all of the ntext columns to nvarchar on a test site and see what the repercussions are.
I would have thought the issue would be when ASPDNSF supply upgrade scripts, which then might fail because you have changed the column types.
nvarchar(max) gives you a bigger column compared to an ntext, but do you really need it? 2^31-1 bytes is a helluva description for a product!
http://www.esedirect.co.uk
--------------------------------------------------------------------------
Using MS 9.2.0.0 with the following customisations:
Lightbox/Fancybox enlarged images;
Auto-suggest searchbox;
Extra product information shown only to our IP Address (such as supplier info, costs, etc.);
Failed transactions emailed via trigger;
Custom app to show basket contents when customer online;
Orders pushed through to accounting systems.
All the above without source!