nick.mcdermaid (4/12/2013)
If I understand correctly, when looking at the same table with different clients, you can see the japanese characters in one, but not in the other? Doesn't that mean the data is in the table, but one client can't handle it properly, so it's a client issue?
Sort of, but not exactly. It was more an issue of the characters converting to question marks from one staging table to another (columns changing from nvarchar to varchar).
The 'correct' data shows as rectangles in SSMS 2005, and Kanji in 2008. So that part is client related.