sohairzaki2005
asked on
Upgrading from SQL 2000 to 2005 and ntext
I am converting a huge db from SQL 2000 to 2005 I have several next fields should I change to nvarchar(max) I known this will improve performance but I did not will that cause any problem Specially I do not want to put my system down it is an active web site I know that in case of upgrading from 2005 to 2008 I have and it is amuse to change next to nvarchar (max) thanks
are you going to move to sql2005 or stay at sql2000 compatability?
do you make extensive use of UPDATETEXT/WRITETEXT?
when do you plan to alter update statements to use the .WRITE phrase instead
I think it would depend on how much application code you need to change to support and test out the
upgrade anyway... as you say moving to sql 2008 this becomes more of a deinite requirement
(you can still use sql 2005 compatability for a while)
do you make extensive use of UPDATETEXT/WRITETEXT?
when do you plan to alter update statements to use the .WRITE phrase instead
I think it would depend on how much application code you need to change to support and test out the
upgrade anyway... as you say moving to sql 2008 this becomes more of a deinite requirement
(you can still use sql 2005 compatability for a while)
ASKER
are you going to move to sql2005 or stay at sql2000 compatability? moving to sql2005
do you make extensive use of UPDATETEXT/WRITETEXT?I am using coldfusion not .net
when do you plan to alter update statements to use the .WRITE phrase instead
I think it would depend on how much application code you need to change to support and test out the
upgrade anyway... as you say moving to sql 2008 this becomes more of a deinite requirement
(you can still use sql 2005 compatability for a while) Not thinking to upgrade to 2008 for a while
do you make extensive use of UPDATETEXT/WRITETEXT?I am using coldfusion not .net
when do you plan to alter update statements to use the .WRITE phrase instead
I think it would depend on how much application code you need to change to support and test out the
upgrade anyway... as you say moving to sql 2008 this becomes more of a deinite requirement
(you can still use sql 2005 compatability for a while) Not thinking to upgrade to 2008 for a while
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
after the new database stabilized (few weeks or month maybe), you can do the exercise of changing the ntext datatype to nvarchar.