Migrating db's from 2000 to 2005 results in truncated columns?

Hi all,

Today I stumbled across something very strange. A couple weeks ago we migrated 2 servers from sql2000 to sql2005, and changed the default colation at the same time. The way I did it was I backed up all the user databases to *.bak files, uninstalled sql2000, installed sql2005 using the new default colation, and restored the databases. Today we discovered any columns that used to be char(xxx) were truncated to char(255), and the leftover went into a new column (i.e. a char(300) column became 2 columns, column1 char(255) and column2 char(45)).

Does this remotely make sense to anyone? I tested this out creating a dummy database and going from a 2k to 2k5 instance with the same colations would not split the columns, however from 2k to 2k5 with a different colation does. And so far it only appears to have affected the char datatype.

(note this is from sql2k sp3a to sql2k5 without sp1)

Is this a bug or am I just whacked?

Thanks

Anyone?|||

I'm moving this thread to the database engine forum, where you're more likely to get help.

Paul

Microsoft Visual Sutdio for Applications has lost the link to .

Hello,

I am struggling with a really ugly problem in SSIS.

I am designing SSIS package where I have a couple of Script tasks. Let's call them Script Task 1 and Script Task 2. Everything was working fine until this morning I added another Script taks (Script Task 3), which was trying to do some rudementary file manipulation. At that point I started getting this message:

"Microsoft Visual Sutdio for Applications has lost the link to .

Your work will be exported to c:\documents and settings\".

This is it! "lost a link to "dot". After this, the VS environment continues to run in debug mode, so it doesn't even crash stirctly speaking. I can stop debugging and continue developing, but nothing would run anymore and I would keep getting the same error. Moreover, after removing Script Task 3 (which seems to be the culprit), I would still keep getting the same error! Only removing all the script tasks completely and then adding them back gets the package to run again.

Any ideas?

Hi Michael,

This is the first time we are seeing this problem. The only thing that I can think that happened is that somehow those scripts got in a bad state.

One way to fix this kind of errors is to try and setting the precompiled property to false on those script tasks, remove all the breakpoints from the scripts, save the package and then reset the precompiled to the desired value and re-add the breakpoints. By doing that the precompiled version of the scripts will be refreshed and hopefully everything will be back in sync.

Also make sure you have SQL Server SP2 installed because it fixes some problems with scripting that might cause these errors.

Another problem might be if you generated script 3 using copy/paste in the package designer from one of script 1 or 2. Some problems regarding that operation were fixed in SP2.

Let me know if that helped.

Silviu Guea [MSFT] SQL Server Integration Services