SAS Portlets, Widgets, Themes and Tutorials for sale

ABSTRACT 

You may have heard about the new cube update feature coming in SAS® 9.2 but may not be sure of just what it
entails. Learn exactly what cube update is and how to get started with it. These "how-to's" will be discussed:
 

• distinguishing between managed and in-place update 
• adding new data as well as new hierarchical members 
• updating existing member properties 
• changing cube captions

INTRODUCTION

After a SAS® OLAP cube is created, it is possible to update the data for the cube without completely recreating it.

The SAS® 9.2 OLAP Server enables you to incrementally update SAS OLAP cubes. An incremental update involves  adding cell data and members to an existing SAS OLAP cube. Incremental updates of a cube are generally faster  than rebuilding the cube from the combined set of input data and update data.  
 
There are several decisions you must make before you create your cube that will make the incremental update  process run smoother. You will need to decide how to structure your cube and the input data as well as choose a  method of update. The update procedure itself has many options that you can use to control what parts of the cube  will be updated. Once the cube is updated, there are maintenance tasks that you should perform periodically.  As you  update the cube, query performance may start to degrade.  This is due to the extra racks of data that are added  during the update.  One maintenance task is to coalesce the racks of data into a single aggregation table in order to
restore performance.

 Avoid Growing Pains: New Cube Update Features You Should Know About

ABSTRACT

INTRODUCTION

Web Report Studio is a web-based reporting tool with many capabilities added over the course of three major  releases.  The upcoming release adds many new features driven by requests from users.  This paper organizes the  key capabilities in Web Report Studio 4.2 into categories. Virtually all features affect the user interface, and the first  section describes key UI enhancements that are designed to improve the user experience. New prompting makes  reporting more flexible for consumers and can minimize the number of reports needed.  OLAP cubes enable fast  navigation of your data, and enhancements will get you the specific rollups you need. Visualization helps you  understand report information quickly, and Web Report Studio 4.2 includes a number of graph enhancements, such  as annotated reference lines. Report linking has been enhanced to let users navigate from high level information, now  including geographical maps, to specific report sections and even SAS stored processes. Web Report Studio users  will be able to better leverage the expertise of SAS programmers and many useful enhancements, such as  comments, have been made to encourage collaboration.  Data driven hyperlinks in tables allow report consumers to  click on text or images that go to another URL, such as a product page or an email client so users can take action. 

Further, administrators will be able to customize the capabilities exposed in WRS for a group of users, and a built-in  scheduler simplifies configuration for single instance deployments.  These and many other enhancements in Web  Report Studio 4.2 will help your organization better leverage information and intelligence by making SAS BI more
pervasive.

 What’s New in SAS Web Report Studio 4.2

ABSTRACT

INTRODUCTION

IT infrastructure Library (ITIL) Service Support processes define “change control” as the process of controlling change, including requests for change, approvals, execution, and validation. “Change management,” on the other hand, is the process responsible for handling changes to IT infrastructure or IT services (Stickel 2005).

Change control is the process to coordinate changes to content in a given environment in a rational manner. Typically, organizations set up three environments: a playpen environment (Development), a quality assurance environment (Test), and a published environment (Production). Changes can be made in an ad hoc fashion in Development (DEV) and promoted to Test (TEST) for quality assurance. After the content is validated, the changes can be promoted to Production (PROD) for broad end-user consumption. Promoted content is usually not editable by end users, and any changes must go back through the DEV/TEST/PROD process.

With SAS® 9, the SAS® Metadata Server is at the core of the intelligence platform. The SAS Metadata Server facilitates the sharing of content across SAS applications to provide a consistent representation of the business to all constituents in your organization. As a result, it is critical that the information that is surfaced to end users in a production environment has been rigorously protected from the impacts of change. This paper focuses on “change control” for the SAS Metadata Server. This is intended for SAS system administrators who are familiar with the SAS® 9 architecture and the role that the metadata server plays. We focus on the tools available for promoting metadata.

Metadata Promotion in SAS 9.2

ABSTRACT

• ability to include or exclude members from aggregated values (parent values) 
• member Level Security user interface
• subsetting report data using Information Map Filters
• roles controlling report functionality 

ABSTRACT

INTRODUCTION