BookmarkSubscribeRSS Feed
☑ This topic is solved. Need further help from the community? Please sign in and ask a new question.
_maldini_
Barite | Level 11

I'm using SAS University Edition to manage SAS datasets provided to me by a third party. I am noticing a message in my log when use the datasets: 

 

"NOTE: Data file CARDIA.C1260REQ06_29_2023.DATA is in a format that is native to another host, or the file encoding does not match the session encoding. Cross Environment Data Access will be used, which might require additional CPU resources and might reduce performance."

 

Is this issue something I should be worrying about? If so, how can I address it? 

 

Thanks.

1 ACCEPTED SOLUTION

Accepted Solutions
ballardw
Super User

This is normal. There are two major cases that can have different impacts.

One is the original data set is just from a different operating system and generally doesn't have major issues.

 

The second is if the character values are encoded using a different data encoding system, such as a double-byte system that contains foreign language characters, such as Chinese, and your system uses a WLATIN encoding then you will lose data in the character conversion.

 

Suggestion: create a new copy of the file such as with a data step, which will repeat that message.

Look at the values. If there aren't any problems just use the copy you made to avoid the message. If it appears you have lost text, symptoms include characters that look incorrect for the variable or empty boxes then you may have to consider some other options to preserve the text.

View solution in original post

1 REPLY 1
ballardw
Super User

This is normal. There are two major cases that can have different impacts.

One is the original data set is just from a different operating system and generally doesn't have major issues.

 

The second is if the character values are encoded using a different data encoding system, such as a double-byte system that contains foreign language characters, such as Chinese, and your system uses a WLATIN encoding then you will lose data in the character conversion.

 

Suggestion: create a new copy of the file such as with a data step, which will repeat that message.

Look at the values. If there aren't any problems just use the copy you made to avoid the message. If it appears you have lost text, symptoms include characters that look incorrect for the variable or empty boxes then you may have to consider some other options to preserve the text.

Ready to join fellow brilliant minds for the SAS Hackathon?

Build your skills. Make connections. Enjoy creative freedom. Maybe change the world. Registration is now open through August 30th. Visit the SAS Hackathon homepage.

Register today!
Mastering the WHERE Clause in PROC SQL

SAS' Charu Shankar shares her PROC SQL expertise by showing you how to master the WHERE clause using real winter weather data.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 1 reply
  • 575 views
  • 1 like
  • 2 in conversation