In SAS/ACCESS^® Interface to Snowflake 9.2, using the SQL procedure to read in a Snowflake table with the SCANSTRINGS=yes LIBNAME option might not reduce the lengths of the character variable when you rename the character column.

As a result, slower performance can occur, and the resulting data set needs more space for storage. 

Workaround

To work around this issue, use the SCANSTRING= data set option. 

Additional Resources

See SAS Note 70901, "Snowflake character column lengths might not be shortened with the SCANSTRINGS=YES LIBNAME or Data Set options" for the original issue with the SCANSTRINGCOLUMNS option not reducing the length. 

See SAS Note 71029, "The SCANSTRINGCOLUMNS=yes option might not reduce the length of the VARCHAR Data Type Columns in a Snowflake table" for issues when there is more than one column in the table.