I am a relative newbie to all things SAS. I work on a site where we have numerous SAS DI Studio jobs, most of which are grouped into SAS Flows for overnight batch runs.
However, we do not appear to have any useful mechanism for performing SAS DI Studio job source code control:-
1. We currently export the individual SAS DI Studio job as a xxxx.spk file and store this in a third party version control system.
But the issue we run into is that although we have all the different versions of the SAS DI Studio jobs in xxxxx.spk files - these are stored as Binary files and we cannot see what the differences are between versions.
I would be interested to know how do the rest of the SAS community deal with version control?
As Linus mentioned, you could deploy the code to a source code file and save that to the versioning system, which would allow you to do more effective differencing. The next version of DI Studio will include automation for versioning of packages, as well as some ability to compare the current version of an object to the ones in source control.
I wouldn't have mentioned it if it weren't coming soon;). This will be in our next release - version 4.3. The planned release date is September of this year, but as you know, these things can change.
This is very very good news. I cannot wait to get my hands on this. Version control in DIS is many people's list (not in the least of those that are involved in product selection and compare DIS to its competitors!).
This versioning feature will be documented Help files and a chapter in the Users Guide.
The 2025 SAS Hackathon Kicks Off on June 11!
Watch the live Hackathon Kickoff to get all the essential information about the SAS Hackathon—including how to join, how to participate, and expert tips for success.
Need to connect to databases in SAS Viya? SAS’ David Ghan shows you two methods – via SAS/ACCESS LIBNAME and SAS Data Connector SASLIBS – in this video.