• support.sas.com
• KNOWLEDGE BASE
• SUPPORT
• LEARNING CENTER
• COMMUNITY
•  

Hot Topics

• Updates for SAS 9.2 (March 2008)
  See the compatibility calculator to determine whether you need to migrate your libraries to SAS 9.2. Use the PROC MIGRATE calculator to find the right example code for your migration.
  
  
• Get a Smarter COMPARE
  Validation tools for the MIGRATE procedure now work with CEDA and provide additional details about catalogs, indexes, and integrity constraints.
  
  
• Start Planning
  See Getting Started for the most efficient pathway through all of the SAS®9 migration documentation.
  
  
• Coexistence
  Many SAS®9 products can install side-by-side with SAS 8.2 with very good compatibility. See Peaceful Coexistence: SAS®9 and SAS 8.2 for details.
  
  
• Sample Validation SOP
  See an example SOP: SAS Installation Qualification / Operational Qualification (PDF) (updated 19 May 2008) for the pharmaceutical industry.

Related Links

• SAS Notes
• Glossary
• Install Center
• Section 508 Accessibility
• Expanded Table of Contents
• Contact Us

Taking Inventory of Roles

Migration

Taking Inventory of Roles: Details

These roles should be thought-provoking, not literally assigned. See the previous page, Taking Inventory of Roles, for more context.

Project leader

may be thought of as the "owner" or manager of the migration project. This individual works with a SAS sales representative to determine the proper amount and kinds of site licenses. This role does need to be clearly assigned. They will make management-level decisions.

If your organization is large, then the project leadership might be a hierarchy containing several levels of responsibility. The top-level leader might not perform any hands-on installation tasks, but rather planning and shepherding. Each workgroup or business unit would then have a project leader.

Installer

performs the installation tasks. This may be the SAS Installation Representative, the individual who registered with SAS to receive the Installation Kit.

If the organization is large, then probably the IT division installs SAS. On the other end of this spectrum, individuals would install SAS on their own machines, especially if running on Windows. Your migration might include both of these kinds of installers. The project leader must identify who will install SAS for each workgroup.

Data owner

might have a job title of data warehouse administrator or database administrator. Data can be stored in SAS files or in third-party software such as Oracle or Teradata.

IT representative

provides additional hardware resources (for example, disk space) as needed, and helps tune and configure the hardware.

Hardware and software optimization specialist

sizes the hardware requirements and tunes the hardware and software for optimal performance. See the tuning topic in the execution stage.

Tester

validates the SAS installation and hardware to ensure a seamless transition. This individual can help debug any problems.

Security officer or administrator

provides authentication like password and user ID, or grants operating environment privileges.

Internal documentation specialist

documents the migration process and any migration instructions that are site-specific.

SAS user

is anyone who accesses SAS software. List the individuals by workgroup. You will learn how they use SAS by asking questions in the Scheduling topic. Some SAS users are "data owners" as well.

Programmer

writes PROCs and DATA steps, either in the SAS interactive windowing environment or in a text editor to be run as batch jobs.

Custom application developer

writes applications that wrap complex SAS analytics in a simple user interface, so that users can send queries and run reports without writing programs themselves. This developer usually owns the code and might use a SAS product like AppDev Studio or SAS/IntrNet. This individual is very familiar with custom applications' components and knows what needs to be migrated.

Custom application user

accesses a simple user interface to SAS. Although they might not have any knowledge of the underlying SAS code, this user can identify the processes that are business-critical and those that can better accept disruption.

Analyst

like a programmer, an analyst writes PROCs, DATA steps, and ad hoc queries but uses a more interactive programming interface such as SAS Management Console or Enterprise Guide.