EG: Can I Work in Another Process Flow While A Query Is Running In A Different Process Flow?

[Fistful_Dollars]

I am running a query in one process flow (Process Flow A).  There is another process flow (Process Flow B) with completely different data.  Can I work in Process Flow B while running a query in Process Flow A without messing anything up in the query that is running?  Thank you.

[JuanS_OCS]

Hello @Fistful_Dollars,

if there are no dependencies on resources (data sets or other kind of files) between the 2 flows, you can always open a second EG session and run the second flow from there, and it should work as long as long as you have the resources on the server and your PC.

Kind regards,

Juan

[LinusH]

Define "work".
If you open the project in a separate EG session you might get inconsistency between contents of the separate flows.
I think you can work parallel in same session, but submitting code parallel is not recommended (if it even works).

[ChrisHemedinger]

Usually, EG has just one connection to specific SAS session.  So if you're working with SASApp (for example) and it's busy with a query, you're not going to get much response from it if you try to start something else using different data on the same server.  Only one code submission will run at a time.

@JuanS_OCS's suggestion of a second EG session solves that.  Another EG session->a different connection to SASApp.

If you have multiple servers, such as SASApp1 and SASApp2, then you can multitask in the same EG project view as long as you keep the interactions completely separate.  That can be tricky, as one server will be treated as the "default" server and certain actions might get pushed there first -- even if you intend to switch the server as you define the task.  (Example of an action that will first hit a default server: importing a CSV file from your local machine.)  

[SASKiwi]

I think it is worth pointing that you can continue to edit a SAS program while a project or another program is running in the same EG session. As long as the action you are doing does not require interacting with your SAS server (like editing a program) then that should be OK.