Problem Note 64434: Saving a Microsoft SQL Server table within SAS® Cloud Analytic Services takes longer than expected
 |  |  |  |  |
When you save a Microsoft SQL Server table that is loaded in CAS, the Save operation takes longer than expected. The table might initially load into CAS within seconds. However, any subsequent Save action for the same table can take minutes.
A workaround exists in programming environments like SAS® Studio. It requires both a caslib and a SAS library that are defined for the same Microsoft SQL Server source.
The following syntax demonstrates this workaround. Note that you already need to have a CAS session and have assigned the appropriate caslib. Also, you need to set the appropriate connection options for the LIBNAME statement:
proc delete data=saslib.table-name ;
run ;
data saslib.table-name ;
set caslib.table-name ;
run;
Click the Hot Fix tab in this note for a link to instructions about accessing and applying the software update.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Data Connector to Microsoft SQL Server | Linux for x64 | V.03.04 | V.03.05 | Viya | Viya |
An update for this issue is available for SAS Viya 3.4. For instructions on how to access and apply software updates, see the Updating Your SAS Viya software section in the SAS Viya 3.4 for Linux Deployment Guide at
http://documentation.sas.com/?softwareId=administration&softwareVersion=3.4&softwareContextId=softwareUpdates| Type: | Problem Note |
| Priority: | high |
| Topic: | Data Management ==> Access ==> Export Data Management ==> Data Sources ==> External Databases ==> MS SQL Server |
| Date Modified: | 2019-11-07 09:35:59 |
| Date Created: | 2019-07-05 08:46:44 |