Problem Note 68200: A value that is stored as a NUMERIC data type might be read into SAS® with a different value than how it is stored in a Google BigQuery table
 |  |  |  |  |
When reading a numeric value from a Google BigQuery table, the value that is read into SAS might differ from the value that is stored in the database. This issue might occur when the following is true:
- The data type of the variable is NUMERIC.
- The value is an integer.
- The BULKUNLOAD=YES LIBNAME or data set option is used.
- The value is between 4,611,686,019 and 9,007,199,254,740,992 (the largest integer that SAS can store exactly).
The issue will not occur for every value in that range. The issue might also occur with non-integer numeric values although the value range might differ. This problem is unrelated to any loss of precision that might occur when SAS is unable to store the non-integer value exactly as it appears in the database. For a better understanding of numeric precision, see SAS KB0036211, "Choosing your degree of numeric precision."
The workaround for this issue is to use the BULKUNLOAD=NO option or to switch to using the READ_MODE=STORAGE option instead to help with Read performance.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS/ACCESS Interface to Google BigQuery (on SAS Viya) | Linux for x64 | V.03.05 | Viya | ||
| SAS System | SAS/ACCESS Interface to Google BigQuery | Linux for x64 | 9.42 | 9.4 TS1M7 | ||