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


hi all,

today stumbled across strange. couple weeks ago migrated 2 servers sql2000 sql2005, , changed default colation @ same time. way i did backed the user databases *.bak files, uninstalled sql2000, installed sql2005 using new default colation, , restored databases. today discovered columns used char(xxx) truncated char(255), , leftover went new column (i.e. char(300) column became 2 columns, column1 char(255) , column2 char(45)).

 

does remotely make sense anyone? tested out creating dummy database , going 2k 2k5 instance same colations not split columns, 2k 2k5 different colation does. , far appears have affected char datatype.

(note sql2k sp3a sql2k5 without sp1)

 

is bug or whacked?

 

thanks

anyone?


SQL Server  >  SQL Server Database Engine



Comments

Popular posts from this blog

Motherboard replacement

Cannot create Full Text Search catalog after upgrading to V12 - Database is not fully started up or it is not in an ONLINE state

Remote Desktop App - Error 0x207 or 0x607