What I expect: Some option similar to (in-/out-)encoding in a libname or filename statement, that enables me in a U8 session, to read the data from OLE DB like I can do in an English session. It is important that that can be done in a central point and no corrections of the dataset are necessary since that would affect a lot of code that I can't/won't change. >From the documentation, in-/outencoding should do exactly that. The annoying thing is that it is not implemented in the OLE DB engine... And about the reverse: The text written with U8 gives ä ` ´ ñ in English (as expected) ... View more

The database contains texts in wlatin1, as 'E460B4F1'x, placed there by another legacy application. The literals in the snippet were only for demonstration purposes. Those texts are normally imported from other systems (file interface, e.g. csv, xlsx) and I can handle the encoding with options. ... View more

Dear Tom! Thank you for your reply. (Sorry, it is not possible to attach a screenshots. I hope, the characters will show correctly in this forum...) There are 2 problems: 1) Reading data that is already in the DB 2) Writing updates into the DB For Simulation: data testline; length text 20; * E4 60 B4 F1; text = "ä ` ´ ñ"; run; data mydblib.test; set testline; run; Ad 1) With proc sql noprint; select text into :check from mydblib.test; quit; %put ✓ executed in SAS (English) I get as wanted: ä ` ´ ñ The SQL run in SAS (U8) on the same data (not created with SAS (U8)) gives something that I can’t copy paste from the log. But it looks like: • ` • • in the log and � ` � when displaying the table (Yes, there are only two ?, but length is 20!) An export to a csv gives correct characters. ------------------ Ad 2) On the other hand, when I append data with SAS (U8), proc append data=testline base=mydblib.test; run; SAS (English) reads: ä ` ´ ñ from the second line (in the log, when displaying the table and exporting to CSV) ---------------------- So as long as there is no encoding-Option on just that connection I will have to use the workaround of starting two SAS sessions, one for the communication with the MSSQL server (SAS(English)), another for the rest of the system (SAS(U8)). 😞 ... View more

Thank you for the hints. I don't think that this is a problem on the Microsoft side. As I wrote above: When I start SAS with the English configuration script, it works correctly. But because of the connection to UTF8 encoded sources I want to start it with the u8 configuration. ODBC is not a solution because of the SingleSignOn approach used in our MSSQL. And I am not allowed to change the table in the DB. So the only way to go is to start SAS (Englisch), get the table from the db. Start SAS (Unicode) and proceed... ... View more

NOTE: Copyright (c) 2016 by SAS Institute Inc., Cary, NC, USA. NOTE: SAS (r) Proprietary Software 9.4 (TS1M6 MBCS3170) Licensed to XXXXX. NOTE: This session is executing on the X64_10PRO platform. NOTE: Analytical products: SAS/STAT 15.1 SAS/ETS 15.1 SAS/IML 15.1 NOTE: Additional host information: X64_10PRO WIN 10.0.18362 Workstation NOTE: SAS initialization used: real time 1.10 seconds cpu time 0.92 seconds NOTE: AUTOEXEC processing beginning; file is XXXXX.sas. NOTE: Libref XXXXX was successfully assigned as follows: Engine: V9 Physical Name: XXXXX NOTE: Libref XXXXX was successfully assigned as follows: Engine: V9 Physical Name: XXXXX NOTE: AUTOEXEC processing completed. 1 %let server=XXXXX; 2 %let dbase=XXXXX; 3 4 libname mydblib oledb 5 init_string="Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=True; 5 ! Initial Catalog=&dbase;Data Source=&server" outencoding="wlatin1" schema=dbo; --------- 278 NOTE: Libref MYDBLIB was successfully assigned as follows: Engine: OLEDB Physical Name: WARNING 278-63: The option OUTENCODING is not implemented in the OLEDB engine. 6 7 libname mydblib oledb 8 init_string="Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=True; 8 ! Initial Catalog=&dbase;Data Source=&server" schema=dbo; NOTE: Libref MYDBLIB was successfully assigned as follows: Engine: OLEDB Physical Name: 9 proc sql; 10 create table test as 11 SELECT * 12 FROM mydblib.test(encoding='wlatin1'); WARNING: The option ENCODING is not implemented in the OLEDB engine. 13 quit; NOTE: PROCEDURE SQL used (Total process time): real time 0.20 seconds cpu time 0.00 seconds ... View more

Thanks for checking. Here is the log... ... View more

Dear Chris!   As you can see in the description of my problem: Yes, I did. And the error message was: WARNING: The option ENCODING is not implemented in the OLEDB engine.   BR, Juergen ... View more