![old version stat transfer old version stat transfer](https://www.timberlake.co.uk/media/wysiwyg/interface_large_wwwsa.png)
I'm fine with SAS having a closed/proprietary format for storing data. But would be nice to have an open transport format as well that maintained variable names, labels, formats, and numeric precision. I see a lot of posts online where a DBA is asking "what the #$?!! can I do with this SAS dataset that was dropped in my hands." But having outsiders reverse-engineer this can only work so well. Then as mentioned, stat/transfer and formerly DBMS copy are probably scriptable. I'm casually aware that there are R /python / etc folks who have tried to read SAS datasets with varying success (and updates with SAS versions etc), and I would guess cozyroc has written their own ODBC diver to do similar (?). So yeah, there are alternatives to delivering SAS datasets, but the core question remains, if a non-SASsy DBA receives a SAS dataset, what is the best/easiest way for them to read it into their database? So maybe XML to keep the metadata with the file. Sure, but with csv you lose metadata and have to think about maintaining precision. Run-time efficiency is not a critical issue, as will only be loading two tables, and will be less than a million records. I'm hoping to recommend to him a way he could load the data that he would be comfortable with, and be able to manage the load using tools he is already familiar with (SQL server management studio, etc), rather than introduce the execution of SAS jobs into his processes.
![old version stat transfer old version stat transfer](https://static.helpjuice.com/helpjuice_production/uploads/upload/image/2723/direct/1581418720446-session-history.png)
Now the DBA has a project where a SAS dataset will arrive weekly and need to be loaded automatically. And may eventually go that way.īut currently this DBA manages all the data loads with non-SAS tools, and we only connect to the database from SAS to read data. I know we could write a SAS job to load the data.
#Old version stat transfer driver
The person loading the data does have a PC SAS license (and access to a SAS BI server), so it looks like the SAS ODBC driver may be an option. Looking for options/guidance on best ways to load a SAS dataset into a SQL server database, having the load process be executed by SQL server (SSIS or whatever) rather than as a SAS job. As part of their message, the agencies also urged Regeneron to transfer technology used to make its monoclonal antibody to other manufacturers so that lower-cost biosimilar versions could be made.