Differences between SAS EG and SAS DI?

Occasional Contributor
Posts: 6

Differences between SAS EG and SAS DI?

Hi Everyone,

My Institution uses SAS EG for a lot of its processes however recently my team has been asked to run a project on SAS DI. Having never used SAS DI i was hoping to get some advice from those more knowledgeable.

  • What are the advantages of SAS DI over EG?
  • Is there any significant coding differences between the two?
  • Is it possible to convert SAS DI code to SAS EG and is it worth it?

I'd love to hear your opinions and anecdotes.


Valued Guide
Posts: 3,206

Re: Differences between SAS EG and SAS DI?

Eguide is a coding environment in a more classical way. There are helpers to generate code like query builder, but it is code based.


The concept of DI is quite different it is not code based instead it is metadata based. With the relations of metadata (records/fields) wiht the transformations pattersn jobs are generated. The jobs are seen as SAS - code.

There you the difference. Where code/tasks is the object you are working on wiht Eguide wiht DI it are the results of that generation as like the SAS-metadata is your source-code and the relulting sas-code is the executable.

---->-- ja karman --<-----
Super User
Posts: 1,229

Re: Differences between SAS EG and SAS DI?


I wrote a blog post a little while ago on my perspective on the difference. As Jaap mentions, it is metadata driven.

Hope it helps: http://bi-notes.com/2013/11/sas-enterprise-guide-difference-sas-di-studio/

Kind Regards,
Ask a Question
Discussion stats
  • 2 replies
  • 3 in conversation