• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Sunz2010   Bill Gibson   Managing Sas Environment
 

Sunz2010 Bill Gibson Managing Sas Environment

on

  • 2,401 views

 

Statistics

Views

Total Views
2,401
Views on SlideShare
2,392
Embed Views
9

Actions

Likes
0
Downloads
30
Comments
0

2 Embeds 9

http://www.sunz.net.nz 6
http://www.slideshare.net 3

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Sunz2010   Bill Gibson   Managing Sas Environment Sunz2010 Bill Gibson Managing Sas Environment Presentation Transcript

    • Considerations in Managing your SAS Environment SUNZ 2010 16 February 2010 Bill Gibson CTO, SAS ANZ Copyright © 2006, SAS Institute Inc. All rights reserved.
    • Agenda What environments (Dev/Test/Prod, Discovery & Operational, Business Continuity) should you have? Administration – daily, weekly and periodic tasks • Back-ups • Monitoring your environment • Software Maintenance User Support Trouble shooting and working with SAS Support Copyright © 2006, SAS Institute Inc. All rights reserved.
    • Environment Types Development Test Production Software Test Playpen UAT BAU Dev/Test Discovery Operational Business Continuity/DR Copyright © 2006, SAS Institute Inc. All rights reserved.
    • Copyright © 2006, SAS Institute Inc. All rights reserved.
    • Software Environments - Single Environment Simple and cheap to set up and manage. Risks around business continuity if issues arise. Risk of breaking system by • Runaway usage • Incorrect maintenance application • Hardware error Need to evaluate time to recover from an outage, and the business impact. Copyright © 2006, SAS Institute Inc. All rights reserved.
    • 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) Copyright © 2006, SAS Institute Inc. All rights reserved.
    • Discovery & Operational Environments Copyright © 2006, SAS Institute Inc. All rights reserved.
    • Complex Enterprise Wide Architecture Copyright © 2006, SAS Institute Inc. All rights reserved.
    • Sample Complex Configuration- Detail Active/passive Metadata Clustered Mid Tier Grid enabled compute Tier Copyright © 2006, SAS Institute Inc. All rights reserved.
    • SAS Administration Requires competency around both operating system and SAS (+ people skills) Not necessarily a full time role SAS Platform Administration Training mandatory Focus should be on preventing problems, not fixing them Critical to have a SAS Administration role with suitable competencies. (Ref: The Many Hats of the SAS® Administrator Copyright © 2006, SAS Institute Inc. All rights reserved.
    • Administration – Back-ups (daily) Metadata Server Backups are essential. • Operating system back-ups cannot back-up a running metadata server successfully. It must be paused. • Make sure the SAS back-up is archived to a separate location. • SAS Standard install provides 31 day rolling back-ups. Back-up Content Server /Table Server at the same time as metadata Back-up SAS Config directory tree before/after each config change Copyright © 2006, SAS Institute Inc. All rights reserved.
    • Best Practices for Backing Up and Restoring Your System Best Practices for Backing Up Your SAS System Copyright © 2006, SAS Institute Inc. All rights reserved.
    • Tip: Create Admin Metadata “Playpen” Server Selective Restore of Archived Metadata Versions • Restore production metadata back up to playpen ia file copies • Selectively export content • Import required objects back to production environment Does not require a complete environment, just a metadata server which can be started as needed Copyright © 2006, SAS Institute Inc. All rights reserved.
    • Monitoring Your Environment Disk Space • Regular cleanup of orphaned work libraries • Out-of-space is a major cause of production job failure • Monitor space during overnight batch processing System Resources • CPU • Memory • I/O performance Copyright © 2006, SAS Institute Inc. All rights reserved.
    • Windows I/O and Memory Management Generally poorly understood. I/O is typically a bottleneck with multi-GB files – and I/O by default goes through Windows file cache. Look at SGIO (which avoids cache) – use Bufno=n000 Understand Windows Memory management: http://blogs.msdn.com/ntdebugging/archive/2007/10/10/the- memory-shell-game.aspx Copyright © 2006, SAS Institute Inc. All rights reserved.
    • SAS 9.2 and the SAS Administrator Major advances in System Administration in 9.2 • Attend the changes in Platform Administration training • Browse the What’s New • Try the new features out! Copyright © 2006, SAS Institute Inc. All rights reserved.
    • SAS® 9.2 Audit and Performance Measurement SAS Metadata Server Audit Reporting • Administrative authorization and authentication modifications • Administrative group and userid access control modifications • Userid authentication and authorization patterns • Userid authentication and password failure attempts SAS Enterprise BI Server analytic server performance usage • Metadata Library Reporting • PROC and DATA library reports • SAS OLAP Server Cube usage • SAS Stored Process Server usage and user reporting • SAS analytic server processor utilization reports SAS Enterprise BI Environment Status Reports, • Web application server and services availability • Analytic server tier availability • Analytic server tier response time reporting • Real-time alert feature for failure state conditions Copyright © 2006, SAS Institute Inc. All rights reserved.
    • Copyright © 2006, SAS Institute Inc. All rights reserved.
    • Software Maintenance Generally proactive, scheduled maintenance is recommended. For 9.2, install maintenance releases in a scheduled maintenance outage. If you do this you probably do not need to apply pro-active hot fixes as well. Hot fixes are generally only available at the current maintenance release level. Details at support.sas.com- search “Maintenance Release” Copyright © 2006, SAS Institute Inc. All rights reserved.
    • User Management – Real Life Examples 6TB of data in SAS Data Sets 30,000 SAS programs – no understanding of who created what, when, and what is obsolete. User program that uses 400GB of work space, whole system slows down when it runs. (some tuning reduced space required by 95%) Copyright © 2006, SAS Institute Inc. All rights reserved.
    • Suggestions for Managing Users Create, communicate and “enforce” Best Practices • Define standard directory / metadata trees Provide avenues for knowledge sharing • Web site • User forums • Mail lists Publicise successes Business Intelligence Competency Centre Concept - see SAS Web Site Copyright © 2006, SAS Institute Inc. All rights reserved.
    • Enterprise Guide Standard Locations for Projects Versioning Strategy Project Size & Complexity • Don’t put everything in one project • Separate Data Preparation from Analysis & Reporting Understand How EG interacts with 3rd party databases Copyright © 2006, SAS Institute Inc. All rights reserved.
    • DI Studio Standard Metadata Structure Meaningful Names • Temp Tables • Process Objects Create sensible size jobs • Consider restartability Copyright © 2006, SAS Institute Inc. All rights reserved.
    • Example Copyright © 2006, SAS Institute Inc. All rights reserved.
    • Trouble Shooting & Working with SAS Tech Support 1. Learn to use Support.sas.com 2. Plan and test remote access for support (WebEX) 3. Provide complete logs, not just extracts • Learn how to create diagnostic logs and set logging levels 4. Single error messages and screenshots of limited use. 5. Provide information on “What is” and “What is not”. Copyright © 2006, SAS Institute Inc. All rights reserved.
    • Conclusions A well managed SAS environment is a productivity aid for all users Administrators need to have blend of IT & SAS skills Monitoring your environments allows issues to be anticipated, and avoided. Appropriate standards, well communicated & monitored, facilitate development and maintenance. Copyright © 2006, SAS Institute Inc. All rights reserved.
    • Questions & Feedback Copyright © 2006, SAS Institute Inc. All rights reserved.
    • References The Many Hats of the SAS® Administrator Fabian Robinson, Shiva Srinivasan PJM Interconnection, Norristown, PA SAS Global Forum 2009 177-2009 Optimizing SQL performance with SAS Enterprise Guide® Best practice paper SAS and Teradata Center of Excellence Copyright © 2006, SAS Institute Inc. All rights reserved.