nvarchar(255) to nvarchar(max) conversion issues

Forum for users of SQL Compare schema synchronization utility

Moderators: JonathanWatts, Chris Auckland, David Atkinson

nvarchar(255) to nvarchar(max) conversion issues

Postby jumpmedia » Thu Nov 29, 2007 5:46 pm

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
jumpmedia
 
Posts: 2
Joined: Thu Nov 29, 2007 5:41 pm

Postby Michelle Taylor » Fri Nov 30, 2007 12:43 pm

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.
Michelle Taylor
 
Posts: 529
Joined: Mon Oct 30, 2006 12:45 pm
Location: Red Gate Software

Postby jumpmedia » Mon Dec 03, 2007 2:11 pm

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
jumpmedia
 
Posts: 2
Joined: Thu Nov 29, 2007 5:41 pm

Postby Michelle Taylor » Mon Dec 03, 2007 3:35 pm

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.
Michelle Taylor
 
Posts: 529
Joined: Mon Oct 30, 2006 12:45 pm
Location: Red Gate Software

Postby eddie davis » Tue Jul 29, 2008 4:23 pm

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
eddie davis
 
Posts: 943
Joined: Wed Jun 14, 2006 3:47 pm
Location: Red Gate Software


Return to SQL Compare Previous Versions

Who is online

Users browsing this forum: No registered users and 0 guests