Chinese encoding problems encountered when using microsoft sql server php MsSql server

However, after importing to sqlserver 2005, I found that its Chinese encoding only supports GB and UCS-2 (unicode 16), so the query displayed directly in the database is correct, but when it is displayed using PHP's UTF9 encoding, it is all garbled.
I have found a lot of information, including suggestions on using mssql, freetds, odbc, ado, or directly transcoding every query and write. However, in actual testing, I found that Ado's method is easy to use.
The code is as follows:

Copy the code The code is as follows:

Copy the code The code is as follows :

//print("The next line generates an error.
");
//printaline("PLEASE?");
//print("This will not be displayed due to the above error.");
?>
//$conn = odbc_pconnect("myodbc", "sa", "cvttdev", 0);
//$c Access Driver (*.mdb); DBQ=".realpath("mydb.mdb");
$c Server};Server={192.168.22.40};Database=sugarcrm_db;UID=sa;PWD=123456;";
$c );
$query= odbc_do($connid,"select id,name from accounts");
?>

while(odbc_fetch_row($query))
{ echo '';
$name = odbc_result($query,2);
$id=odbc_result ($query,1);
echo '';
echo '';
echo ' ';
}
?>

ID	Title< /th>
'. $id .'	'. $name .'

Query results:

The above introduces the Chinese encoding problems encountered when using microsoft sql server php MsSql server, including the content of microsoft sql server. I hope it will be helpful to friends who are interested in PHP tutorials.

ID	Title
114b0775 -d9b2-db90-fcda-4a2f2cd7cdbd	Mirai Shoji Co., Ltd. 629487
1d270085-a588-9ea7-584c-4a2f2c8d1a5b	Fabriqué Interationål 79436
23	�� ��
36ea2575-fe34-61b0-e5ae-4a2f2c791d22	Berufskolleg für Elektrotechnik 65790
3834261a-fd48-9d4a-be40-4a2f2c5fc256	Berufskolleg für Elektrotechnik 529523
52c9 652c-82c8-ec2b-72ae-4a2f2c3a58d6	Mirai Shoji Co., Ltd. 42138
78931a0e- f582-f406-8a56-4a2f2c3741b0	Butée Torique 700010
989473f7-6b7b-fed3-12a1-4a2f2c320645	A.B.ケアブレBünde -Mitte 203765
d72c42c9-9e1d-b926-d931-4a2f2c2a3100	Berufskolleg für Elektrotechnik 27682
e97002f1-035f-91d3 -4592-4a2f2f780e01	zhh
	because odbc is not set up either code page location.