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

collation issue when upgrade to 2008 R2 Expand / Collapse
Author
Message
Posted Monday, September 10, 2012 5:11 AM


Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Friday, March 21, 2014 9:46 AM
Points: 387, Visits: 1,078
Hi All,

I am waiting for project in whcih I need to upgrade sql server 2000 to 2008R2. The main thing is collation going to be changed.

It will be a side by side migration. Apart from this, I do not have any more details).

I plan to do scripting source objects and bcp them to destination.
Can anyone please advise how to do (better option) this upgrade with collation change?

Thanks
Post #1356657
Posted Monday, September 10, 2012 6:36 PM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, March 10, 2014 10:49 PM
Points: 194, Visits: 194
Collation change can become very messy, especially when you're upgrading at the same time. I'm sure you'll be trying out this method before doing it in production system.

Anyhow, I can suggest the following "high level" points for the implementation:

1) Generate script to create your <database> and "all" objects within the database including object level permissions. Make sure collation is not used when generating the script

2) Modify the database name, collation name and file/filegroup names if required in database creation script. Only run the database creation script at this stage on the target instance. This will create a new empty database with required collation.

3) Check the remaining database script to find any deprecated feature used in the script and modify to use 2008 R2 alternative. You will also need to check the deprecated features in the target database after the migration. See the link below for details on how to check and fix deprecated features.

http://www.mssqltips.com/sqlservertip/1857/identify-deprecated-sql-server-code-with-extended-events/

4) Create all the database objects except Foreign Keys and Check constraints

5) Copy the data to new database using either bcp out/in or import/export wizard. Make sure identity insert is allowed in the data transfer for tables with identity columns

6) Apply the Foreign key and Check constraints.

7 ) If required, compare the two schema's for any differences excluding the collation.

Hope it'll help.

Cheers,
Fahim




Fahim Ahmed
Knowledge is a journey, not a destiny
Post #1357078
Posted Monday, September 10, 2012 10:03 PM


Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Friday, March 21, 2014 9:46 AM
Points: 387, Visits: 1,078
Thank you for your timely reply. I will have a note of these steps.
Post #1357125
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse