+1  A: 

What is your database collation? Are you able to store Korean strings with any other data access technology? What is the type of the username column, and is it accurately mapped in LINQ to SQL?

I suspect that something in the database isn't set up correctly to allow full Unicode. I very much doubt that this has anything to do with LINQ itself.

The other thing to check is that you're actually getting the right data in the first place. There are often several places where things can go wrong - you need to validate each place separately to see where the data is being corrupted. I have a short article on this which you may find helpful.

Jon Skeet
.beingaskeduser column is in varchar...and the code is working on alpanumeric string but when I get a korean string, this happens
jamal
A: 

It sounds like you are storing Korean text in a varchar/text column which is not using a Korean collation. Thea easiest fix is to change the column type to nvarchar/ntext.

The nchar column types store Unicode data, whereas the char and varchar types store single byte characters in the specified collation.

Lachlan Roche
Thanks man, appreciate it everything works good now.
jamal