Problem Note 70901: Snowflake character column lengths might not be shortened with the SCANSTRINGS=YES LIBNAME or Data Set options
 |  |  |  |  |
Using the SQL procedure to read in a Snowflake table with the SCANSTRINGS=yes LIBNAME or data set options might not reduce the lengths of character variables when the query includes the DISTINCT keyword. Instead, the length of the column remains as defined in the database.
This issue can result in slower performance, and the resulting data set needs more space for storage.
A workaround is to use the FEDSQL procedure or explicit pass-through with the SQL procedure.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Note: The hot fix addresses issues when the Snowflake table contains only one column. See SAS Note 71029 for issues when there is more than one column in the table.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS/ACCESS Interface to Snowflake | Microsoft® Windows® for x64 | 9.42 | 9.4 TS1M7 | ||
| Linux for x64 | 9.42 | 9.4 TS1M7 | ||||
| SAS System | SAS/ACCESS Interface to Snowflake (on SAS Viya) | Linux for x64 | 2020.0.5 | Viya platform | ||
A fix for this issue for SAS/ACCESS Interface to Snowflake 9.43 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/L9B.html#70901A fix for this issue for SAS/ACCESS Interface to Snowflake 9.42 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/I9Y.html#70901| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2024-11-04 16:37:48 |
| Date Created: | 2024-07-23 13:42:18 |