Red Gate forums :: View topic - nvarchar(255) to nvarchar(max) conversion issues
Return to www.red-gate.com RSS Feed Available

Search  | Usergroups |  Profile |  Messages |  Log in  Register 
Go to product documentation
SQL Compare Previous Versions
SQL Compare Previous Versions forum

nvarchar(255) to nvarchar(max) conversion issues

Search in SQL Compare Previous Versions forum
Post new topic   Reply to topic
Jump to:  
Author Message
jumpmedia



Joined: 29 Nov 2007
Posts: 2

PostPosted: Thu Nov 29, 2007 5:46 pm    Post subject: nvarchar(255) to nvarchar(max) conversion issues Reply with quote

Hi, I have version 6.1.0.53 and we are converting nvarchar(255) columns to nvarchar(max). We were surprised when the compare reported that the column might be truncated, and also when it insisted on dropping the table and recreating it (Which causes us problems as the tables are replicated).
Is this expected behaviour, or functionality that can be improved?
_________________
Dave Needham.... Jump Media
Back to top
View user's profile Send private message MSN Messenger
Michelle Taylor



Joined: 30 Oct 2006
Posts: 529
Location: Red Gate Software

PostPosted: Fri Nov 30, 2007 12:43 pm    Post subject: Reply with quote

The truncation warning is a bug we fixed in 6.2 - if you check for updates (on the help menu), you should get a message about this free point release and be able to download it.
Back to top
View user's profile Send private message
jumpmedia



Joined: 29 Nov 2007
Posts: 2

PostPosted: Mon Dec 03, 2007 2:11 pm    Post subject: Reply with quote

Yep, that warning is fixed.

What would be great to get more clarity on is why the tables are being dropped rather than an alter column or new column and rename method being used.

This is pertinent to us because we have replication set up, and recreating the table causes its GUID to change, hence breaking replication.
_________________
Dave Needham.... Jump Media
Back to top
View user's profile Send private message MSN Messenger
Michelle Taylor



Joined: 30 Oct 2006
Posts: 529
Location: Red Gate Software

PostPosted: Mon Dec 03, 2007 3:35 pm    Post subject: Reply with quote

The tables are being dropped and recreated because in SQL Server 2000, you couldn't ALTER COLUMN a varchar to a text field, and the same logic that we use to avoid trying to do that is triggering on the difference between a varchar(255) and a varchar(max).

I've raised a bug about this, as SQL Server 2005 can cope with ALTER COLUMN between these types, and hopefully we can get it fixed in the next version.
Back to top
View user's profile Send private message
eddie davis



Joined: 14 Jun 2006
Posts: 941
Location: Red Gate Software

PostPosted: Tue Jul 29, 2008 4:23 pm    Post subject: Reply with quote

I am pleased to inform you that we have fixed this problem in the recently released SQL Compare V.7.

If you have a valid Support & upgrades option, you can download SQL Compare V.7 using the 'Check for updates' mechanism (SQL Compare GUI ->Help ->Check for updates)

or download using this link: HERE.

SQL Compare V.7 will install along side any previous versions of the software.

Many Thanks
Eddie Davis
_________________
Eddie Davis
Technical Support Engineer
Red Gate Software Ltd
E-mail: support@red-gate.com
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Reply to topic All times are GMT + 1 Hour
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group