Problem Note 70880: SAS/ACCESS® Interface to Google BigQuery now supports threaded reads with READ_MODE=STORAGE
 |  |  |  |  |
SAS/ACCESS® Interface to Google BigQuery now supports threaded reads when using the Storage API. This functionality is available via the DBSLICE= data set option and DBSLICEPARM= LIBNAME/data set option.
If you do not specify the DBSLICE= option but request a threaded read, the parallel processing is based on multiple streams that return data. With the DBSLICE option, you specify the slicing WHERE clauses that are used for the threads:
To use these options, you must also set READ_MODE=STORAGE (or MODE=PERFORMANCE, which sets READ_MODE=STORAGE). Otherwise, these options are ignored.
These options might help improve read performance. There is some overhead that occurs with these options, so SAS recommends performing benchmarking to find the optimal setting for 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 | Linux for x64 | 9.42 | 9.4 TS1M7 | ||
| SAS System | SAS/ACCESS Interface to Google BigQuery (on SAS Viya) | Linux for x64 | 2020.1.1 | Stable 2024.06 | Viya platform | Viya |
A fix for this issue for SAS/ACCESS Interface to Google BigQuery 9.42 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/K2L.html#70880| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2024-07-18 08:49:52 |
| Date Created: | 2024-07-08 17:55:10 |