SFT - Customer Best Practices

October 16th, 2009

Jerry Blevins

2 >

Summary of the Topic - The Plan (Spring 2008)

SummaryThere is a need and opportunity for Teradata customers to have a

Testing Best Practices Document

GoalPublish article in the TD Magazine

Provide a BP White Paper accessible to all customers

Winter / Spring 2009 TUG presentations

ApproachCharter a joint team of SFT Members / TD Interface / PM

- TD interface who accesses engineering and TCS experts

3 >

SFT Best Practices Project Plan

Project Plan1. Create draft of White Paper

2. Use White Paper as basis for Abstract & Presentation

3. All SFT members to send best practice examples to Team Leads for as many sections as possible

4. Sub-teams are responsible for their respective sections: White Paper Presentation

5. Integration Team Responsible for integrating the sub-team submissions from the

White Paper and Presentation. Designates to be interviewed for magazine article.

6. Review progress during SFT monthly meetings

4 >

The Deliverables: By Customers for Customers

Customer Best Practices for Teradata Upgrades

Major Software Upgrades

Table of Contents1.Introduction2.The Upgrade Process

Major Database Software Upgrades, Defined Upgrade Process Overview Diagram

3.Project Management4.Upgrade Planning

Research the new versionIdentify your dependent applicationsPre-upgrade BenchmarkingRegression Testing

5.User Communication6.Change Control7.Upgrade Client Software

Upgrade Teradata Tools and Utilities8.Upgrade BAR Software9.Teradata Pre-Upgrade Preparations10.Teradata Upgrade11.Post-Upgrade Steps12.Project Closeout13.Closing

5 >

Customer Best Practices for Teradata Major Software Upgrades Presentation

2 >

Agenda

• Who We Are

• Document Introduction and Highlights> Upgrade Process Overview

> Project Management and Upgrade Planning

> Communication and Change Control

> Upgrade Client and BAR Software

> Pre-upgrade Steps

> The Upgrade Window

> Post Upgrade Steps

• Closing

6 >

The Deliverables: Teradata Magazine Article

As members of the Service Focus Team (SFT), a committee that's part of the PARTNERS User Group, we work closely with Teradata on issues related to support services and other areas that fall beyond the scope of product enhancements. From our collective experience we've developed a list of nine tips that we hope you will find helpful in your next upgrade endeavor.

Ask the Experts

Take It From Us9 tips for a smooth upgrade

By the Teradata Service Focus Team

Members of the Teradata Service Focus Team work with Teradata to address your support-related issues.

Whether they're called "minor" or "major," all database software upgrades must be completed hitch-free and be smoothly integrated with client software and third-party applications.

7 >

The Deliverables: By Customers for Customers again

Customer Best Practices for Teradata UpgradesMajor Hardware Upgrades

Table of Contents1.Introduction2.The Upgrade Process for Teradata Hardware

Upgrade Process Overview Diagram3.Project Management4.Upgrade Planning

Plan for capacityResearch environmental requirementsReview network requirementsPre-upgrade Benchmarking

5.User Communication6.Change Control7.Environment Changes

Data Center:MVS Environment:Node OS Environment:Network Environment:

8.BAR Implications9.Pre-Upgrade Preparations with Teradata10.Teradata Upgrade11.Post-Upgrade Steps12.Project Closeout13.Closing

8 >

Customer Best Practices for Teradata Hardware Upgrades Presentation

• Who We Are

• Document Introduction and Highlights

> Upgrade Process Overview

> Project Management and Upgrade Planning

> Communication and Change Control

> Upgrade Client and BAR Software

> Pre-upgrade Steps

> The Upgrade Window

> Post Upgrade Steps

• Closing

Agenda:

Customer Best Practices for Teradata Hardware Upgrades

9 >

Upcoming TUG Meetings: Presentations Owners?

• Sept 30 - Turkey – Istanbul – • Oct 27 - Australia - Canberra – • Oct 28 - Australia - Melbourne – • Oct 29 - Australia - Sydney – • Nov 5 - UK & Ireland - London – • Nov 11 - Germany - Frankfurt -• Nov 12 - Scandinavia - Stockholm -• Nov 13 – Finland & the Baltics - Helsinki  -  • Nov 17 – Egypt – Cairo - • Nov 17 – Netherlands – Amsterdam - • Nov 18 – France - Paris -• Nov 19 – Spain – Madrid -• Nov 25 – Austria – Vienna -• Nov 26 – Italy – Rome - • Nov 26 – Japan – Tokyo - • Nov 27 – UK & Ireland – Dublin - • US/Canada will have 10 meetings from March 1 - May 31

> 6 more in August/early September 

10 >

Teradata Magazine Article

• Submitted a proposal to the magazine team to do a second in a series of articles from the SFT.

Ask the Experts

Take It From UsTips for a smooth hardware upgrade

By the Teradata Service Focus Team

11 >

Going Forward Approach?

1. What topic is next on the priority list for best practices?

• Software – done

• Hardware – done

• Testing and Benchmarking before/after upgrades (ties SW & HW together) – Next?

• Teradata Operations Guide?

• BAR - FUTURE

• Security - FUTURE

• T@YS Education – FUTURE

2. How should we structure the current and next document? • Make next topic a new, separate document?

• Consolidate the Software & Hardware documents into a single upgrades document?

• Should we review and update existing documents on an annual basis?

3. Do we continue to develop PPT decks for presentation at TUG’s? • Update existing Software Upgrades deck to include Hardware?

• Create a separate Hardware Upgrades deck?

12 >

Possible Whitepaper - Teradata Operations Guide

Possible Contents

Ongoing Maintenance • Perform Teradata Space Monitoring, Assignment and Maintenance• Perform Teradata Database Integrity Validation• Perform Teradata Resource Usage Set-up, Support and Reporting• Monitor Technical Alerts• Perform Initial Problem Isolation / Identification / Documentation• Perform Initial Problem Research via Support Link• Provide Incident / Problem Management

Operating System Administration • Perform Space Monitoring and Assignment (Disks and Other Devices)• Perform Resource Usage Set-up, Support and Reporting (Memory, CPU and • Storage)• Provide User Access and Set-up• Start-up, Shut-down and Reboot Teradata Server Operating System

Data Backup and Recovery • Develop Backup/Recovery Strategy and Procedures • Perform Periodic Backups of Operating System Nodes• Restore Operating System on Teradata Server Nodes• Perform Periodic Backups of Database and Applications• Restore Teradata Database• Perform Disaster Recovery Procedures Administration

System Performance • Perform Capacity Planning• Perform Availability Tracking, Measurement and Reporting• Develop Performance Monitoring System Procedures• Establish / Maintain Proper Job / User Priorities• Perform Operating System Tuning• Perform Teradata System Level Tuning• Perform General Application Tuning (Data Block Size, Defrag) • Provide Ongoing System Performance Monitoring and Reporting• Monitor Network Usage / Performance

13 >

Possible Whitepaper - Teradata Operations Guide

Functionality / Applications • Perform Query Management• Perform ApplicationDesign / Development / Testing• Monitor Application Space• Investigate Application Problems / Performance Issues• Perform Application Tuning • Provide Multivendor Management

Operations • Perform Real-time Fault Error Monitoring / Trending• Perform System Health Checks• Develop / Maintain Operations Run Book• Monitor Production Job Flow• Monitor System Utilization• Effect Job Recovery When Needed• Manage Host / LAN Connectivity • Perform Network Administration (Support, Reporting and Monitoring)

Database Administration / Security • Provide User Access and Set-up (Accounts)• Maintain Account Passwords and Resource Limits• Perform Security Log Reviews / Reporting• Establish / Maintain Access Rights to Database Objects • Start-up, Shutdown and Restart Teradata Database System