How to call/launch a standalone SAS batch process from a SQL Server Integrtion Services process?

Reply
New Contributor
Posts: 2

How to call/launch a standalone SAS batch process from a SQL Server Integrtion Services process?

I have a request to automate a process which must run a SAS program and then use SSIS to import the results from the SAS process into a MS SQL Server based data warehouse.  I know very little about SAS so I am looking for anyone who has technical knowledge of SAS and perhaps has called/launched SAS from a SSIS Execute Process Task?  If so, can someone provide the steps in which you were successful in launching the SAS standalone executable engine or perhaps if you have a server version how you called the server version to run the SAS process?

Thanks.

Scott

Super User
Posts: 3,102

Re: How to call/launch a standalone SAS batch process from a SQL Server Integrtion Services process?

The simplest way to execute a SAS batch job is to do it from an operating system command line. This link for Windows explains the details:

http://support.sas.com/documentation/cdl/en/hostwin/64812/HTML/default/viewer.htm#p16esisc4nrd5sn1ps...

The SAS command would have to be executed on the server where SAS is installed.

An alternative approach might be for the SAS process to be scheduled independently, then have SAS load the results as tables into SQL Server. This is likely to be easier to set up rather than trying to "control" SAS from SQL Server.

New Contributor
Posts: 2

Re: How to call/launch a standalone SAS batch process from a SQL Server Integrtion Services process?

Thank you for pointing out some different options for this.  At this point the decision has been made not to invest in a SAS server and they are looking at other alternative ways of getting the data into the SQL Server database.  I will however let them know that your last option might be a viable alternative.

Thanks.

Scott

Super User
Posts: 5,255

Re: How to call/launch a standalone SAS batch process from a SQL Server Integrtion Services process?

Did you have SAS and you didn't want invest in another SAS server license?

As another flavour of the alternative to have SAS populate SQL Server (requires a SAS /ACCESS license), you could have SAS create some csv files, which your SSIS process could import.

Data never sleeps
Ask a Question
Discussion stats
  • 3 replies
  • 722 views
  • 0 likes
  • 3 in conversation