Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SQL Server 2000 upgrade issue... Expand / Collapse
Author
Message
Posted Thursday, September 19, 2013 9:06 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Wednesday, April 16, 2014 1:47 PM
Points: 54, Visits: 481
I'm attempting to migrate SQL Server 2000 database to SQL Server 2008. After reviewing the results of the upgrade advisor (no issues), I restored the database to 2008. It was subsequently identified that one of the fields had its length changed from 30 to 10 (nvarchar!10), null).

My experience with upgrades is limited (first time effort). Is there something I missed when moving the database over? Copied the backup to the new environment and restored the database.

Any comments / URLs would be appreciated. Thanks.
Post #1496450
Posted Friday, September 20, 2013 5:42 AM
SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Thursday, April 17, 2014 5:22 AM
Points: 881, Visits: 1,352
I have upgraded/migrated at least 300 databases from SQL 2000 to SQL 2005 and SQL 2005 to SQL2012 and never experienced the issue that you mentioned.

My technique is to take a backup of the older version database and restore it to the new version of sql server. I then change the compatibility level to the new level and update the stats.

We've never had an issue with data types changing. I'm not sure how they could change when performing a database restore.

It almost seems as though SSIS or the import/export wizard was used in your case and not a restore but you said you performed a database restore. The Unicode data types are typically <default> for many of the import/export tables if you are allowing the wizard to create the tables.

That's a very interesting problem. Sorry I can't really help.

Steve



Post #1496820
Posted Friday, September 20, 2013 1:01 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Wednesday, April 16, 2014 1:47 PM
Points: 54, Visits: 481
You gave me an idea which tentatively has resolved our problem. I noticed you went from 2000 to 2005. I was going from 2000 to 2008. While Microsoft supports 2000 to 2008, we changed the steps going from 2000 to 2005 to 2008. No testing has been performed however we did confirm the column length did not change. So far so good.

Thank you for commenting...
Post #1497007
Posted Thursday, September 26, 2013 12:46 PM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Thursday, April 17, 2014 8:43 AM
Points: 1,201, Visits: 2,661
That is very bizzare. I have upgraded many dbs from 2000 to 2008 and never seen it change the attribute of a column....


Post #1499016
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse