Including the MAX_CHAR_LEN= and DBSASTYPE= options might result in incorrect data when using SAS/ACCESS® Interface to Google BigQuery


Using the MAX_CHAR_LEN= LIBNAME statement or data set option along with the DBSASTYPE= data set option might result in incorrect data in some of the variables. 

This issue occurs when the length specified for the variable designated with the DBSASTYPE= option is longer than the length specified with the MAX_CHAR_LEN= option. The variables referenced with the longer lengths in the DBSASTYPE= option are assigned to the correct length, but the data in the variable might be correct up to only the length specified by the MAX_CHAR_LEN= setting+1. The rest of the data (up to the full length) might contain data from variables after the last variable.