SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


collation issue when upgrade to 2008 R2


collation issue when upgrade to 2008 R2

Author
Message
SQL Show
SQL Show
SSChasing Mays
SSChasing Mays (655 reputation)SSChasing Mays (655 reputation)SSChasing Mays (655 reputation)SSChasing Mays (655 reputation)SSChasing Mays (655 reputation)SSChasing Mays (655 reputation)SSChasing Mays (655 reputation)SSChasing Mays (655 reputation)

Group: General Forum Members
Points: 655 Visits: 1078
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
ultimate sql
ultimate sql
SSC Veteran
SSC Veteran (231 reputation)SSC Veteran (231 reputation)SSC Veteran (231 reputation)SSC Veteran (231 reputation)SSC Veteran (231 reputation)SSC Veteran (231 reputation)SSC Veteran (231 reputation)SSC Veteran (231 reputation)

Group: General Forum Members
Points: 231 Visits: 256
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
SQL Show
SQL Show
SSChasing Mays
SSChasing Mays (655 reputation)SSChasing Mays (655 reputation)SSChasing Mays (655 reputation)SSChasing Mays (655 reputation)SSChasing Mays (655 reputation)SSChasing Mays (655 reputation)SSChasing Mays (655 reputation)SSChasing Mays (655 reputation)

Group: General Forum Members
Points: 655 Visits: 1078
Thank you for your timely reply. I will have a note of these steps.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search