Chris Hemedinger has blogged a number of very good reasons why you would move fomr Base SAS to Enterprise Guide. He has also outlined the things you will loose.
In my experience most SAS programmers are forced by their cpmpanies to move to EG rather than do so willingly (but I amnot saying the move is a wrong one). There are a number of reasons that this move is enforced on them, including:
- Reducing License costs, by moving from desktoplicenses to server ased licenses
- Increased code reuse by non SAS programmers
- Increased documentation, via EG’s semi self documenting features
One of the area I find base SAS Programmers struggle with is the whole idea of Metadata vs Physical table data. So I would recommend spending a bit of time on this with them.
At the moment we would love to move our DI Studio code to EG for one of our projects. The reason?
In EG you can see the log file as the code run’s, in DI Studio you have to wait until it finishes (assuming it does finish).
DI Studio provides the ability to see where in the process flow your job is at, but for now we write our code in DI Studio, then grab it and run it in EG so we can keep up with what it is doing.
Is it true that you can see the log file as the project runs in EG? If so, how do I do this? Right now I must wait for all of the EG code to execute (or an error occurs) before the log file is accessible. thanks.
Note: I am using EG 4.1…
Hi Dale
Once you have started a node running in EG,right click on it and select View Log.
The log file will then be shown and additional information displayed at the bottom as the job runs.
Cheers
Shane
Hi,
I have moved to EG, I had a code that I was running on base SAS.
I tried to run it on EG it gives out an error with no suggestion on how I can change it to work.
EG is a good idea but it is not helpful if users are not given assistance in the cause of this issue.
Thanks.