image
Suhaila

0

What’s the difference between SAS Enterprise Guide and SAS DI Studio?


What is the difference between SAS Enterprise Guide and SAS DI Studio? What are the advantages among them?



- Suhaila
image

Lili96

0

What are the differences between SAS Studio and SAS Enterprise Guide?

Both SAS Studio and SAS Enterprise Guide provide a point-and-click interface to SAS that enables you to create reports, graphs, and charts; access SAS servers and data; and analyze data. Both products also include ready-to-use tasks for analysis and reporting as well as a color-coded SAS language editor. The primary difference between SAS Studio and SAS Enterprise Guide is that SAS Studio is a tool that you can use to write and run SAS code through your web browser. SAS Enterprise Guide is a Microsoft Windows client application that you install on your machine.

The following table lists some additional differences:

enter image description here

with reference to:http://support.sas.com/software/products/sasstudio/faq/SASStudio_vsEG.htm



- Lili96
image

SandyTang

0

Difference between SAS Enterprise Guide and SAS Studio

SAS Enterprise guide

  • EG is more common in firms with a smaller team of analytics. This is because programs on EG are far more understandable by a person who is new to the firm. Given the high attrition rate in analytics industry, it becomes very essential for such firm to hedge their risk by using the SAS Enterprise guide instead of Base SAS.

    • You develop a certain traditional routine much faster on EG than on Base SAS.
  • It is much easier to comprehend the flow using EG.

SAS Studio

  • Provides a point-and-click interface to SAS that enables you to create reports, graphs, and charts; access SAS servers and data; and analyze data.

  • Includes ready-to-use tasks for analysis and reporting as well as a color-coded SAS language editor.



- SandyTang
image

Bjergsen

3

SAS Data Integration Studio

SAS Data Integration Studio is used to create and maintain data warehouses and data marts, which are specialized stores of data that have been prepared for effective reporting and analytics. Data experts, such as database administrators and IT specialists — people who support other folks who have to create reports — use SAS Data Integration Studio. Like SAS Enterprise Guide, this is a client application that runs on your desktop and provides an intuitive user interface, but it can connect to SAS and databases that run on machines all over your organization.

Since we are more familiar with SAS enterprise guide, ill put a pic of SAS DI studio here.

enter image description here SAS Enterprise Guide

SAS Enterprise Guide provides a modern, easy-to-use interface to much of the power of SAS. SAS Enterprise Guide is used by SAS programmers, business analysts (who might or might not have programming skills), and statisticians. It’s a Microsoft Windows application that can connect to SAS; you can use it to drive the SAS analytics engine running on a mainframe, UNIX, or other remote machines as a server application. SAS Enterprise Guide is like a general store for SAS, where you can get a little bit of everything that SAS has to offer.



- Bjergsen
image

JiaQii

1

It’s about the Metadata
What do I mean by this? Well, in EG you work with tables and SAS code (either with EG tasks or hand written code). If you’re a SAS programmer whose upgraded from SAS Display Manager (aka BASE SAS) then you now get the benefit of a program editor with autocompletion, built-in syntax highlighting, integrated help and automatic code formatting. If you are an analyst then you get the power of being able to generate SAS code for your reporting and querying needs via point-and-click tasks within your EG project. In both situations you generate SAS code (perhaps even a stored process) all working off SAS tables that may have libraries assigned in metadata… and there is that word… metadata.

As I’m sure you know the general definition of metadata is “data about data“. So what is that… it’s details about the data you are working with. For example, if you have a customer table in your Oracle database then that metadata is about the Oracle library engine (assuming that you are using SAS/Access to Oracle), connection details to the Oracle database, the column attributes (such as name, type, length, formats etc), when the table was created, modified and any security access controls etc. So why is this important…

With the SAS 9 platform the SAS metadata server and associated metadata repositories are the heart of SAS. The SAS 9 Intelligence Platform Overview document provides a great background to help understand how all the pieces in the SAS platform fit together and the importance of keeping that metadata heart pumping.


Why do SAS Enterprise Guide Users Care about Metadata?
So as an EG user why do I need to know about SAS metadata? The metadata server enables consistent, centralized storage of information about all the resources in your environment. It stores information about many things including: users, groups, roles, capabilities, tables, columns, libraries, cubes, stored processes, information maps, DI jobs and many more. This means you can access many of these resources in EG without having to set them up yourself. Your administrator has already done this work for you and made it available in metadata so you can concentrate on your projects. enter image description here These EG projects, whilst using metadata are not commonly stored in metadata: they are often stored as .sas files or .egp files outside of metadata. This limits their availability for things like impact analysis, searching, metadata audit and security. DI Studio jobs are represented in metadata with a great deal of detail.


What is the Value of SAS DI Studio?
DI is a metadata-driven visual design tool where you create jobs and their components as metadata objects (potentially within an integrated change management environment). Ultimately SAS code is generated, although it is more of a by-product of the process. The job metadata is the primary “document” and is stored with enough detail in metadata to allow the additional benefits.

DI jobs are generally used for consolidating and managing enterprise source and target data with process flows that extract, transform and load (ETL) operational data into data warehouses and data marts. That process can be simple or complex depending on the organisation. Some organisations may start out using EG as an ETL tool and later realise that they have difficulty managing everything they need to do such as data validation, history, data cleansing (via handy data quality tools such as DataFlux), metadata reporting, impact analysis, complex scheduling of dependencies, and change management across environments (dev, test, prod). enter image description here So that’s why I consider the difference between EG and DI primarily relates to “those SAS jobs being SAS metadata objects“… EG is a great tool for consuming SAS metadata to do querying, reporting and analysis. Whilst EG can be used for basic ETL, when you need enterprise data integration capabilities, DI Studio becomes the better choice. It’s greater use of metadata allows for the management of much more complex ETL processes.

For detailed functional differences between EG and DI, check out the product user documentation: http://support.sas.com/documentation/cdl/en/etlug/65920/PDF/default/etlug.pdf



- JiaQii
image

AlvinYap

0

SAS Enterprise Guide

SAS Enterprise Guide is a point-and-click, menu- and wizard-driven tool that empowers users to analyze data and publish results. It provides fast-track learning for quick data analysis, generates code for productivity and speeds your ability to deploy analyses and forecasts in real time.

Features: enter image description here

SAS Data Integration Studio

SAS Data Integration Studio provides a powerful visual design tool for building, implementing and managing data integration processes regardless of data sources, applications, or platforms. An easy-to-manage, multiple-user environment enables collaboration on large enterprise projects with repeatable processes that are easily shared. The creation and management of data and metadata are improved with extensive impact analysis of potential changes made across all data integration processes. Enabling users to quickly build and edit data integration, to automatically capture and manage standardized metadata from any source, and to easily display, visualize, and understand enterprise metadata and your data integration processes.

Features: enter image description here


Differences between SAS Enterprise Guide and SAS Data Integration Studio

  • • Enterprise Guide does not have a loop construct

  • • Enterprise Guide does not have pre-built auditing, pre and post processing, data validation, lookup, and data loader transformations.

  • • Creating and using indexes in Data Integration Studio is a couple of mouse clicks which is more difficult in Enterprise Guide.

  • • Deploying code is more cumbersome in Enterprise Guide. For each job, an Enterprise Guide project must first be run, exported, and then deployed in SAS management console (if using Platform scheduling). Data Integration Studio allows multiple jobs to be deployed with a single 'click'.

  • • Modifying Enterprise Guide projects can be a little tricky. An Enterprise Guide project can't be edited until it has first been run in the current session (except for custom code). If custom code is being edited, the project must be re-run to ensure the correct code is exported. An easy step to forget.

  • • Data Integration Studio SQL transformation is more advanced than the Enterprise Guide query window. eg for performance tuning, multi-column outer joins (changed under Enterprise Guide 4.3?)


When to use SAS Enterprise Guide

— When you need to integrate an extensive array of analytics with the power of SAS software in an efficient, user-friendly graphical user interface application.

— The need to manage access to corporate data ensuring that users have appropriate access privileges that empower them to react quickly to evolving business conditions with a centralized system.

— Quick access to data for analysis, schedule projects, share results and embed output easily for repeated use – including access to advanced analytics and other SAS capabilities.

— Distribute interactive content to Microsoft Office and Web users.

When to use SAS Data Integration Studio

— When you want to add new source systems easily and manage security centrally. This saves time, shortens learning curves and gives you the information and confidence you need to make data-driven decisions.

— To deliver consistent, trusted and verifiable information.

— When you want to reduce costs by eliminating overlapping, redundant tools and complex system architectures. It minimizes the time and effort associated with piecemeal approaches that entail linking and managing technologies from different vendors – to ensure data credibility, reduce risk and speed results.



- AlvinYap
image

HuiLing

2

A difference is that SAS Enterprise Guide is based on the physical structures of the artifacts you're working with while SAS DI Studio is based on their registered metadata. This means SAS DI Studio is better equipped for a formal workflow of design-build-test while SAS Enterprise Guide is more targeted at ad-hoc, analytical and end-user work.



- HuiLing
image

tyt2315

0

t’s about the Metadata

What do I mean by this? Well, in EG you work with tables and SAS code (either with EG tasks or hand written code). If you’re a SAS programmer whose upgraded from SAS Display Manager (aka BASE SAS) then you now get the benefit of a program editor with autocompletion, built-in syntax highlighting, integrated help and automatic code formatting. If you are an analyst then you get the power of being able to generate SAS code for your reporting and querying needs via point-and-click tasks within your EG project. In both situations you generate SAS code (perhaps even a stored process) all working off SAS tables that may have libraries assigned in metadata… and there is that word… metadata.

As I’m sure you know the general definition of metadata is “data about data“. So what is that… it’s details about the data you are working with. For example, if you have a customer table in your Oracle database then that metadata is about the Oracle library engine (assuming that you are using SAS/Access to Oracle), connection details to the Oracle database, the column attributes (such as name, type, length, formats etc), when the table was created, modified and any security access controls etc. So why is this important…

With the SAS 9 platform the SAS metadata server and associated metadata repositories are the heart of SAS. The SAS 9 Intelligence Platform Overview document provides a great background to help understand how all the pieces in the SAS platform fit together and the importance of keeping that metadata heart pumping.



- tyt2315
Cancel