Migrating To SAS 9.2 by Bill Gibson

Migrating to SAS 9.2
Bill Gibson
CTO SAS Australia and New Zealand
SNUG Q1 2009, 19 March 2009

Copyright © 2009, SAS Institute Inc. All rights reserved. Company Confidential - For Internal Use Only

Migrating to 9.2 - Agenda

 Introduction
 When
 Scenarios
 Tools
 Approaches
 Planning
 Services Available


SAS 9.2 Time Line

• Q3-Q4 2009
• April 2009: General Availability
• Q2 2008 Reporting, OLAP, Business Solutions
Data Integration,
SAS Foundation Foundation Maintenance
Limited availability • Release
May: Forecast Server,
Enterprise Miner,
Text Miner,
Model Manager

SAS 9.2 Value Proposition

 Not just a “minor DOT” release. A major step
forward in SAS technology
Delivers a great deal of customer requested functionality

Customer
Driven
Delivers enhancements
Delivers a giant leap to reduce the cost for IT
in functionality to aid More IT
Productivity and Business units of
productivity of all Friendly managing a SAS
using SAS Environment

SAS 9.2


SAS 9.2

 Major update in Platform Support
• Operating Systems
• Java Application Servers
• 64 bit Windows
− Break the 2G ceiling
 New functionality across all products
 New Baseline Architecture Level
• Minor releases will build on initial versions


Are You Running a SAS 9 Platform?

 Do you have a metadata server?
• Server Based
• EG,
• SAS BI
• SAS Management Console
• Enterprise Miner
• Enterprise Guide
 If you are Foundation only this is not relevant
• Migration will be as per previous releases
• “Only” issue is WIN 64
• No issue reported from the 9.2 C phase.

When to Migrate to SAS 9.2 - Checklist
 Interest & Willingness
Product Mix Availability – during rollout period.
 Types of Migration
• Initial learning environment/playpen, followed by staged
migration of production environment(s)
• Immediate full migration in one project

 Migration Approach
• Joint approach SAS/Partner + customer, where site has SAS
9 skills
• SAS/Partner led project, typically where customer skills are
limited

 Funding - people’s time and money

Migrating to 9.2 – Sample Software Scenarios

1. Single Server, Enterprise Guide Clients
2. Single Server, SAS BI
3. Multiple Servers, SAS DI, BI & Portal
4. Multiple Servers, SAS, ABM & EG


SAS Usage Scenarios

A. Analyst Environment
B. Production Business Analytics System
C. Production Operational IT System
D. Combination of above
• Most often A+B (possibly building models, and
production scoring system)


Migrating to 9.2 – Environmental Scenarios

 Single Deployment – often Type A
 Multiple – Dev / Test / Prod
• Multiple environments on one hardware platform
• Multiple hardware platforms
 Physical Environment Considerations
• Virtual / Partitioned Environments
− VMWARE & others
− UNIX logical partitions
• 9.2 separate hardware available
• Only 9.1.3 hardware
− Outages or parallel running

Dev / Test / Prod in Business Analytics
 Very different from traditional operational
systems
 IT use Dev/Test for data management &
production system creation & maintenance.
 Business users create new content (reports,
analyses, & ad-hoc data management) in
production environment as required.
• May use folder level security to manage status.
 Multiple “applications” hosted on a single
platform.
(see http://www2.sas.com/proceedings/forum2007/204-2007.pdf)

 Migration Planning & Timing must allow for this.
• Synchronisation needed.

How do you perform a migration?

 Choose from the following
approaches
1. Migrate content using the automated
migration tools as a part of the install
process.

2. Install a new SAS 9.2 environment and
promote selected content from 9.1.3

 You can use a combination of these
approaches.


 How do you install and configure SAS 9.2?

Delivery Installation & Configuration

 Electronic  Single entry point – SAS Deployment
Software Delivery Wizard
 Custom DVDs  Ask once and upfront; runs automatically
afterwards
• Includes deployment of initial metadata
• Includes deployment of web apps
 Capture/replay available for batch
deployment


Perform migration with migration tools

 Automated tools to support migration of a 9.1.3
system to 9.2 provide a way for our customers to
preserve their current investment in SAS, while
upgrading to the latest version.



Delivery Installation & Configuration

 Includes complete
migration from 9.1.3 to 9.2
• Configuration
• Content
 SAS Migration Utility


SAS Migration Utility

 The SAS Migration Utility supports deploying
SAS 9.2 based on an existing 9.1.3 environment.
• Analyzes the 9.1.3 Environment
• Creates migration packages that the SAS Deployment
Wizard can read which represents the “full system”
configuration and content from 9.1.3.


System Flow: Migration
9.1.3 System 9.2 System
PLAN File
Old config Extrac Migrated
t Generate config

SMU SDW
[Platform +BI] [Platform +BI]
[ Solution A] [ Solution A]
[Solution B] [Solution B]

Co
Co
ct

rt
po
tra

m

nv
bi

Im
Ex

Old Content New Content

ert
n
e

(metadata, DAV, (metadata, DAV,
RDBMS, etc.) RDBMS, etc.)
Migration
package


Why use migration tools to migrate content?

 Most efficient method for upgrading from SAS
9.1.3 to SAS 9.2.
• Upgrades entire system at one time
• Produces additional reports to understand changes in
security
 Preserves customizations made in 9.1.3.
 Checks whether software is at the required
baseline and supported by the automated tools.


Additional steps after using Tools

 Portal content may need adjusting
• Custom themes need to be redefined
• Custom web applications need to be updated
 OLAP cubes need to be rebuilt
 Custom plug-ins need to be modified
 Manual changes to configuration to exploit 9.2
platform enhancements
• Includes validation of behavior
 Validation & Rollout


Perform a migration using promotion tools

 Promotion is the movement of selected content
from a source system to an already configured
target system.


Why use promotion tools to migrate content?

 System configuration in 9.2 will be different
• Changing hardware
• Different server configurations
 Lots of “garbage” content in the existing 9.1.3
system
 Haven’t fully utilized the platform, so minimal
content involved
 Want to try out functionality and/or validate in
bite size portions


Why not use promotion tools only?

 May be more time intensive
• Requires manual movement of content and it is still
difficult to change the folder structure
• Order of promoting objects is important
 Only a subset of metadata content is supported
• No environment metadata – users, groups, ACTs,
servers
• Extra work for OLAP, Portal
 No automatic security comparison reports


So, how long will a migration take?
 Migration process consists of 4 main phases

 Assess the state of the current environment
 Identify what is “outside the SAS box”
 Determine the hardware deployment

 Create software depot and plan file
 Backup the current environment
 Setup target environment

 Upgrade to SAS 9.2 using SASDW with either migration
or promotion tools
 Implement customizations, if needed

 Validate the new environment
 Resynchronize content
 Rollout SAS 9.2 access to end users

So, how long will a migration take?

 The actual execution of the migration is not the
main portion of time.

Timeline
Planning Preparation Implementation Validation/Rollout
30% 20% 15% 35%


So… How long should I plan for a migration?

 It depends on
• Product mix
• Usage scenario
• Environmental scenario
 Total Time (Plan- Rollout)
• “Happy Path” (simple environment) – 5 to 10 days

• Complex environment – 4 to 6 weeks

• Gnarly environment – 2 to 3 months

Planning Objectives

 Document the 9.1.3 environment
 Set goals for the 9.2 environment
 Choose the best approach for upgrading
• Start over installing SAS 9.2 out-of-the-box and
promote selected content from 9.1.3
• Migrate content using the automated migration tools
• Or, use a combination of these approaches


Planning Should be “SNAP”

 Structure of your 9.1.3 deployment
 Nature of your 9.1.3 content
 Aims for your 9.2 environment
 Period of time for upgrading


Migration Process & SAS/Partner Services
 Migration is something that you will only do once.
 It does not make sense to do it without help from people who
have done it before (many times).
 If technical support get questions from people who have botched
an upgrade, they will advise restarting from scratch, and getting
assistance.
Timeline
Planning Preparation Implementation Validation/Rollout
30% 20% 15% 35%
Assessment Execution Service

Service 2-5 Days - Team of SAS/ Partner & Customer resources


Key “Changes & Enhancements” Training

 What’s New in SAS® 9.2 Business Intelligence
 What’s New in SAS® 9.2 Data Integration
 What’s New in SAS® 9.2 Platform Administration

1 Day Training Courses
 Available from May 2009


Resources

 What’s New in 9.2 Documentation
• http://support.sas.com/documentation/whatsnew/index.
html
 Migrating to 9.2
• http://support.sas.com/rnd/migration/index.html

 SAS ANZ Staff – talk to your account team
• Significant internal preparation well advanced.


Migrating to SAS 9.2 - Summary
 Does take effort over a relatively short time
 Preserves existing content & hardware
 More functionality,
maintainability.
 Baseline for future
expansion of use,
and also for
incremental
SAS upgrades.
 Don’t do it by yourself!
 Next Steps?

Questions?
Next Steps


Migrating To SAS 9.2 by Bill Gibson

More Related Content

What's hot (19)

Similar to Migrating To SAS 9.2 by Bill Gibson (20)

Recently uploaded (20)

Migrating To SAS 9.2 by Bill Gibson