02-04-2014 09:48 AM
I have an EG project with two servers loaded (one local and one remote server). Both servers have their own work library. The "query builder" boxes and "filter and sort" boxes are identified as local and produce data sets in the work of my local server.
The problem is: The data set of my "local" library work (produced by query builder for example) cannot be accessed (and used as input) by the program boxes defined on "remote" server (select server = remote server).
Is there a way to make the communication between both server? Should I redefine every output data sets on the work of my remote server? It could take a long time (and I'm not sure it will work...), I would prefer to find a faster solution...
It seems that both server cannot communicate with each other...
Thanks for your help!
02-04-2014 10:00 AM
The technology that allows one SAS server to talk with another is SAS/CONNECT. With that product, you get utility procedures such as PROC UPLOAD and DOWNLOAD, plus remote library services, that allow you to move/reference data among the SAS sessions.
Assuming that you don't have that available, you can copy any data from one server to another via EG. Use the Tasks->Data->Upload SAS Data Sets and Download SAS Data Sets task. You'll need to reference the actual physical path of a local data file in order to upload it to a remote WORK library.
02-06-2014 04:38 AM
Thanks for your answer! :-)
The next problem is: I build an original SAS EG project. The flow is already constructed but problem (explained above) appears. By using the "upload data set task box", this box seems to create a dubble output data sets for every boxes following the upload task. What is strange is that the two duplicates always refer to the same SAS data set (same name, same library, same server). So, the flow works but visually, it's totally awful: imagine that you find every SAS data sets twice in your EG project...
Thanks for your help everyone,