BI Tools

Tips and tricks for building information maps, OLAP cubes, reports, and dashboards

BI Admin

Learn your way around a SAS BI installation.

Visual Analytics

Learn your way around the SAS Visual Analytics tool

Coding & Data

Extract, transform, and load your data into the SAS BI toolset

Stored Processes

Create and design stored processes like a rock star

8 Comments »

  • Tricia says:

    I wish SAS would create a DI/EG mashup tool. There are features from each that I wish the other one had!

  • Tricia says:

    Good points Quentin!

  • Quentin McMullen says:

    Great post. For me, one big reason I use DI studio for ETL instead of EG is the ability to schedule jobs to run nightly on the server, and automatically email upon execution, completion, errors, etc. The process seems a bit cumbersome (deploy a job, then create a flow, then schedule the flow…) at least on our set up where SAS is using LSF tools to manage the scheduling. But the end result works well. And importantly, with DI Studio the scheduled job runs on the SAS server. It’s possible to schedule EG process flows (http://blogs.sas.com/content/sasdummy/2012/04/17/doing-more-with-sas-enterprise-guide-automation/), but since the EG client runs on Windows, it uses Windows scheduler to start EG. If your PC is off, EG can’t run.

  • “Data management” is a discipline in itself, and Data Integration Studio supports that discipline. It’s one of the specialized interfaces that SAS produces to support in-depth activities in the data management arena.

    SAS Enterprise Guide — while it can be used for just about anything — is not geared towards a specific discipline. You, as the user, must bring your own discipline to the tool. If you want to use EG for detailed data management (or predictive analytics, or production forecasting, or quality control metrics…), you can do that (and people do!), but SAS offers other tools that are more fit for that purpose.

    As you point out, Michelle, SAS Enterprise Guide users are often the beneficiaries of the upfront work done in Data Integration Studio. The outputs of DI support the ad-hoc and production reporting needs of the SAS Enterprise Guide masses.

  • Hi jprins (great to hear from you!),

    I’m pleased to hear that the article gave you some realizations. I find that many sites use EG as an ETL tool and then get to the same point, as yourself. Many reasons why this happens such as: changes in business requirements, changes in the way things are done, growth in a team and the need to have better governance and processes in place such as change management, version control and metadata management. In any case, using the strengths of each tool can be extremely beneficial for an organization.

    I hope your transition to DI goes well and that we get to catch up at SASGF14, where we discuss further.

    Cheers,
    Michelle

  • jprins says:

    Thanks for this article. It made me realize we could benefit from SAS DI studio and not try to use EG for ETL.

  • Tricia says:

    Good point!

  • Divyesh Dave says:

    It is worth mentioning that SAS DI Studio, in addition to having ETL features, also has ELT features. In ELT, “load” is done before “transform”.

    Within DI Studio, there is a pass-through option that enables ELT mode.