We can argue the merits of putting data and code in systems like OneDrive or SharePoint, but the fact is that cloud storage is here to stay. And many customers have their SAS environment in the cloud too, so connectivity between these systems is a necessity. It's increasingly rare for people to have local SAS on their desktop to analyze/ingest local data (including Excel files) from their organization. For documents like these, right now the approach is to use APIs.
With macros we can simplify the operation...a bit...for SAS programmers. I began documenting these methods in 2019 and have evolved them quite a bit since. They can be tricky to set up but once in place, it works great. I have batch jobs that read and write content to SharePoint (or Teams folders) every day.
We have the same challenges here at SAS that others have discussed for large files, code files, and policies such as document retention and sensitivity labels. For code, I do not recommend OneDrive or SharePoint. Git is the standard for keeping and versioning code, and for many companies that's GitLab or GitHub (enterprise/cloud versions that are gated for just them, not the public versions). All of my important SAS code is in GitLab repositories for backup, versioning, and business continuity.
SAS data sets also don't belong in SharePoint or OneDrive, especially big files. That eats into the quota limits that seem large to start with, but when you start throwing in everything that people want to save, it dwindles quickly.
... View more
