March 2, 2011 at 8:35 pm
I am migrating Korea data from oracle to sql server using linked server . I am able to downoad the data but all are like junk charatcers.Can any one help me on this.
This is my configuration for linked server
Provider :MSDAORA
Use remote collation :True .
March 2, 2011 at 11:05 pm
Try Microsoft's Migration assistant tool, I've used it for several migrations, you might need to do some manual changes, but overall a great tool..
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This thing is addressing problems that dont exist. Its solution-ism at its worst. We are dumbing down machines that are inherently superior. - Gilfoyle
March 3, 2011 at 6:24 am
They probably are looking like junk as you are not familiar with the Korean characters used in the data.
Importing oracle data is not too tough but as you said,converting the data into english language is something I have never tried.
sorry if I misunderstood your question
March 3, 2011 at 6:47 am
I suspect the OP is aware of the nature of the data and isn't trying to translate from Korean into English 🙂
I'd suggest reading up about collation.
To put it simply, your server has a default collation, as does your database and individual columns can also be set to a specific collation.
The collation you choose must support the character set of the data you're going to store. The most likely reason for successfully being able to import the data, but not able to view it is that it's being imported into columns with unsuitable collation.
March 3, 2011 at 9:52 am
HowardW (3/3/2011)
I suspect the OP is aware of the nature of the data and isn't trying to translate from Korean into English 🙂I'd suggest reading up about collation.
To put it simply, your server has a default collation, as does your database and individual columns can also be set to a specific collation.
The collation you choose must support the character set of the data you're going to store. The most likely reason for successfully being able to import the data, but not able to view it is that it's being imported into columns with unsuitable collation.
I can understand that some column may not be supporting the original datatype collation but this friend of mine says that he is seeing all the columns as junk:-) So not sure why none of the columns are appearing right!
March 4, 2011 at 8:49 am
Just a thought, are you using nchar/nvarchar/ntext to store your character data?
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply