Note that there are some explanatory texts on larger screens.

plurals
  1. POSQL Server database with Latin1 codepage shows Japanese Chars as "?"
    primarykey
    data
    text
    <p>Three questions with the following scenario:</p> <ul> <li>SQL Server 2005 production db with a Latin1 codepage and showing "?" for invalid chars in Management Studio.</li> <li>SomeCompanyApp client as a service that populates the data from servers and workstations.</li> <li>SomeCompanyApp management console that shows "?" for Asian characters.</li> </ul> <p>Since this is a prod db I will not write to it.</p> <p>I don't know if the client app that is storing the data in the database is actually storing it correctly as Unicode and it simply doesn't show because they are using Latin1 for the console.</p> <p><strong>Q1:</strong> As I understand it, SQL Server stores nvarchar text as Unicode regardless of the codepage or am I completely wrong and if the codepage is Latin1 then everything that is not in that codepage gets converted to "?".</p> <p><strong>Q2:</strong> Is it the same with a text column?</p> <p><strong>Q3:</strong> Is there a way using SQL Server Management Studio or Visual Studio and some code (don't care which language :)) to query the db and show me if the chars really do show up as Japanese, Chinese, Korean, etc.?</p> <p>My final goal is to extract data from the db and store it in another db using UTF-8 to show Japanese and other Asian chars as what they are in my own client webapp. <strong>I will settle for an answer to Q3.</strong> I can code in several languages and at the very least understand some others but I'm just not knowledgeable enough about Unicode. In case you want to know my webapp will be using pyodbc and cassandra but for these questions that doesn't matter.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload