DB2 for IBM I Database Modernization: Object Creation and Access

Total Page:16

File Type:pdf, Size:1020Kb

DB2 for IBM I Database Modernization: Object Creation and Access Agenda Key:23MA Session Number:470182 DB2 for IBM i Database Modernization: Object Creation and Access Tom Mckinley ([email protected]) Lab Services IBM Rochester 8 Copyright IBM Corporation, 2009. All Rights Reserved. This publication may refer to products that are not currently available in your country. IBM makes no commitment to make available any products referred to herein. Agenda • Why modernize with SQL & DB2? • Approaches & Options • Modernizing Database Definitions • Modernizing Data Access • Next Steps © 2009 IBM Corporation Why SQL? • Portability of code & skills • Strategic database interface for industry & i5/OS – Faster performance delivered by SQE only available to SQL-based interfaces – SQL required for certain functions & middleware • J2EE architecture based on SQL interfaces • Data types: BLOB, CLOB, Datalink, ... • Auto-Incrementing Constructs: Sequence & Identity column attribute • Column-level Triggers • Encryption & Decryption functions • Encoded Vector Indices • ... • Enables better positioning of System i as a Database Server • SQL as a programming language can reduce total lines of code • DB2 SMP - parallel database processing © 2009 IBM Corporation Approaches & Options ODBC / JDBC / ADO / DRDA / XDA Network Host Server CLI / JDBC Static Dynamic Extended Dynamic Compiled Prepare Prepare embedded every once and statements time then reference Native SQL (Record I/O) Optimizer DB2 (Data Storage & Management) © 2009 IBM Corporation Approaches & Options SQL Considerations: SQL-created Programs Multi-member & objects multi-format files DDS-created Native* objects Programs *Restrictions: EVIs, LOB columns, UDTs, Datalinks, etc © 2009 IBM Corporation Modernizing Definitions & Objects • Modeling • Terminology • Moving from DDS to SQL DDL • SQL object management • Embedding business logic into database definitions © 2009 IBM Corporation Modernizing Definitions & Objects Data modeling • “Master data” concept –Services created to retrieve data – what if multiple copies exist? • Database normalization –Define a separate table for each related set of values –Define the primary key (surrogate or natural) –Eliminate redundant data –Fifth normal form (5NF) recommended, 3NF at minimum –Establish RI constraints • Also consider –Globalization Normalization © 2009 IBM Corporation Modernizing Definitions & Objects Data Modeling IBM Rational Data Architect (Version 7) • Enterprise data modeling and management – Compare & synchronize – Forward & reverse engineering – Logical file support – Fixpack 003 – Model analyzer for enterprise standard conformance • Database development – SQL Stored Procedures and Function • Trial Download: ibm.com/software/data/integration/rda/ © 2009 IBM Corporation Modernizing Database Objects Terminology SQL i5/OS schema/collection library table physical file view logical file index keyed logical file row record column field log journal © 2009 IBM Corporation Modernizing Database Definitions & Objects Tables vs PFs • SQL Tables compared with Physical Files – Advantages • More data types • Constraint definitions can be included in object source • Faster reads • Longer, more descriptive column names • Data Modeling Tool support • DB2 attempts to automatically journal tables – Disadvantages • Slower writes • No DDM, BUT SQL can utilize DRDA connections • Multi-member files – SQL ALIAS provides solution: CREATE ALIAS JanSales FOR SALES (JANUARY ) © 2009 IBM Corporation Modernizing Database Definitions & Objects Indexes vs LFs • SQL Indexes compared with Keyed Logical Files – Advantages • Encoded Vector Index Structure • 64K Logical Page Size (since V4R2) – more aggressive input – Disadvantages • 8K Logical Page Size – less aggressive input • No support for Select/Omit filtering or join logical files – V6R1 provides new syntax to allow the creation of SQL indexes with selection criteria and derivations © 2009 IBM Corporation V6R1 – SQL Derived Index Example DDS for Existing Select/Omit LF: A R ITEM_FACT PFILE(ITEM_FACT) A ORDERKEY A SHIPMODE A PARTKEY A K ORDERKEY A K SHIPMODE • Equivalent SQL syntax: CREATE A INDEX S sql_selectomitSHIPMODE COMP(EQ 'MAIL') ON item_fact ( orderkey, shipmode ) WHERE shipmode = 'MAIL' RCDFMT item_fact ADD partkey © 2009 IBM Corporation Modernizing Database Definitions & Objects Views vs LFs • SQL Views compared with Logical Files – Advantages • More flexibility in terms of selecting & processing data – CASE expressions & Date/Time functions – Grouping & more advanced Join processing • Can be used as logical files to enhance native functionality – Disadvantages • Views cannot be keyed/ordered – Does that mean SQL Views have slower performance? • NO - assuming you have the right set of indexes/statistics in place for the query optimizer to use • View is used by SQL just to transform data, query optimizer's job to find the best method to speed up selection or sorting • Fastest method may not be a keyed access method © 2009 IBM Corporation Modernizing Database Definitions & Objects DDS to SQL Conversion • System i Navigator Generate SQL Task (QSQGNDDL API) – Useful in converting object definitions from DDS to SQL – Supports physical & logical files • Not all DDS features can be converted, tool will convert as much as possible and generate warnings for unconvertible options (e.g., EDTCDE) • Logical files converted to SQL Views • SQL Field Reference File support not used – Can convert a single object or a group of objects – Output can be edited & saved directly into source file members © 2009 IBM Corporation Modernizing Database Definitions & Objects SQL Object Compatibility • SQL Column & Object names have maximum lengths of 30 & 128, but many i5/OS utilities, commands and interfaces only support a 10-character length. How does that work?!?! – System automatically generates a short 10 character name • First 5 chars with unique 5 digit number CUSTOMER_MASTER >> CUSTO00001 • Might be different each time a specific table is created, depending on creation order and what other objects share the same 5 character prefix • Use i5/OS SQL syntax to specify your own short name – RENAME TABLE (tables & views) & RENAME INDEX – FOR COLUMN clause for columns – SPECIFIC clause for procedures, functions © 2009 IBM Corporation Modernizing Database Definitions & Objects SQL Object Compatibility • Short & Long Name Co-existence Example – Specify the short name at creation: CREATE TABLE dbtest/cusmst (customer_name FOR COLUMN cusnam CHAR(20), customer_city FOR COLUMN cuscty CHAR(40)) – Specify a long name for existing short-name: RENAME TABLE dbtest/cusmst TO customer_master FOR SYSTEM NAME cusmst • If long name specified on SQL Table definition, can also add/control the short name after table created: RENAME TABLE dbtest/customer_master TO SYSTEM NAME cusmst © 2009 IBM Corporation Modernizing Database Definitions & Objects SQL Object Compatibility • RENAME statement can also be used to control the format & file name used by native programs ► Specify the format name (cmfmt) when creating the table CREATE TABLE dbtest/cmfmt (customer_name FOR COLUMN cusnam CHAR(20), customer_city FOR COLUMN cuscty CHAR(40)) ► Use RENAME to specify the short file name (cusmst) for table: RENAME TABLE dbtest/cmfmt TO cusmst ► Use RENAME to specify the long name for SQL interfaces RENAME TABLE dbtest/cusmst TO customer_master FOR SYSTEM NAME cusmst ► V5R4 simplifies control of the record format name with new SQL keyword… CREATE TABLE dbtest/customer_master (customer_name FOR COLUMN cusnam CHAR(20), customer_city FOR COLUMN cuscty CHAR(40)) RCDFMT cmfmt © 2009 IBM Corporation Modernizing Database Definitions & Objects SQL Object Compatibility • What happens to my existing applications if my objects are now created with SQL instead of DDS? IT DEPENDS on your approach! © 2009 IBM Corporation Modernizing Database Definitions & Objects SQL Object Compatibility • Recommend Methodology (documented in IBM Redbook) – Convert Physical file source (PF1) into SQL Table (TAB1) – Delete physical file PF1 – Convert the PF1 DDS source into a Logical file named PF1 that references TAB1 – Change the source for all logical files over PF1 to share format of PF1 and reference TAB1 R PF1 FILER PFILE(TAB1) FORMAT(PF1) • XCase for System i new tool available to automate & manage this conversion methodology – Ensure the right steps are done in proper order – Data modeling tool also available © 2009 IBM Corporation Modernizing Database Definitions & Objects SQL Object Management • SQL Source Management best practices: – Store SQL source in source physical file members just like DDS and “execute” with the RUNSQLSTM instead of CRTPF/CRTLF • Store SQL scripts in PC or IFS files for non-i5/OS change management tools • Generate SQL can be used to retrieve misplaced SQL source from System Catalogs (SYSIBM & QSYS2) • V6R1 RUNSQLSTM supports IFS files and wider margins & CL commands – SQL Table definitions can use Field Reference File CREATE TABLE customer AS (SELECT id cust_id, lname cust_lastname, fname cust_firstname, city cust_city FROM RefFile) WITH NO DATA • May need to adjust process for moving from development to production – Best practice is to re-execute SQL creation script – Save/Restore process for SQL databases documented at: ibm.com/developerworks/db2/library/techarticle/0305milligan/0305milligan.html © 2009 IBM Corporation Modernizing Definitions & Objects SQL & Non-relational data • User-Defined Table Functions – Allows non-relational & legacy data to be virtualized as an SQL table SELECT * FROM TABLE(myudtf('Part XYZ')) – Both
Recommended publications
  • IBM Iseries Universal Connection for Electronic Support and Services
    IBM iSeries Universal Connection for Electronic Support and Services Explains the supported functions with Universal Connection Shows how to install, tailor, and configure Universal Connection Helps you determine communications problems Masahiko Hamada Michael S Alexander Makoto Kikuchi ibm.com/redbooks International Technical Support Organization SG24-6224-00 iSeries Universal Connection for Electronic Support and Services August 2001 Take Note! Before using this information and the product it supports, be sure to read the general information in Appendix A, “Special notices” on page 209. First Edition (August 2001) This edition applies to Version 5 Release 1 of OS/400. Comments may be addressed to: IBM Corporation, International Technical Support Organization Dept. JLU Building 107-2 3605 Highway 52N Rochester, Minnesota 55901-7829 When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. © Copyright International Business Machines Corporation 2001. All rights reserved. Note to U.S Government Users - Documentation related to restricted rights - Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp. Contents Preface . vii The team that wrote this redbook . vii Comments welcome . viii Chapter 1. Extreme Support Personalized (ESP) . .1 1.1 Introduction to ESP . .1 1.1.1 Customer Care Advantage . .1 1.1.2 ESP approach. .3 1.1.3 Benefits for customers. .4 1.2 Available applications in electronic support . .5 1.2.1 Electronic Customer Support (ECS) connection . .5 1.2.2 Service Agent . .6 1.2.3 Consolidated inventory collection using Management Central .
    [Show full text]
  • IBM AIX Version 6.1 Differences Guide
    Front cover IBM AIX Version 6.1 Differences Guide AIX - The industrial strength UNIX operating system AIX Version 6.1 enhancements explained An expert’s guide to the new release Roman Aleksic Ismael "Numi" Castillo Rosa Fernandez Armin Röll Nobuhiko Watanabe ibm.com/redbooks International Technical Support Organization IBM AIX Version 6.1 Differences Guide March 2008 SG24-7559-00 Note: Before using this information and the product it supports, read the information in “Notices” on page xvii. First Edition (March 2008) This edition applies to AIX Version 6.1, program number 5765-G62. © Copyright International Business Machines Corporation 2007, 2008. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Figures . xi Tables . xiii Notices . xvii Trademarks . xviii Preface . xix The team that wrote this book . xix Become a published author . xxi Comments welcome. xxi Chapter 1. Application development and system debug. 1 1.1 Transport independent RPC library. 2 1.2 AIX tracing facilities review . 3 1.3 POSIX threads tracing. 5 1.3.1 POSIX tracing overview . 6 1.3.2 Trace event definition . 8 1.3.3 Trace stream definition . 13 1.3.4 AIX implementation overview . 20 1.4 ProbeVue . 21 1.4.1 ProbeVue terminology. 23 1.4.2 Vue programming language . 24 1.4.3 The probevue command . 25 1.4.4 The probevctrl command . 25 1.4.5 Vue: an overview. 25 1.4.6 ProbeVue dynamic tracing example . 31 Chapter 2. File systems and storage. 35 2.1 Disabling JFS2 logging .
    [Show full text]
  • IBM Powervp Introduction and Technical Overview
    Front cover IBM PowerVP Introduction and Technical Overview Liviu Rosca Stefan Stefanov Redpaper International Technical Support Organization IBM PowerVP: Introduction and Technical Overview August 2015 REDP-5112-01 Note: Before using this information and the product it supports, read the information in “Notices” on page v. Second Edition (August 2015) This edition applies to Version 1, Release 1, Modification 3 of PowerVP Standard Edition (product number 5765-SLE). This document was created or updated on August 14, 2015. © Copyright International Business Machines Corporation 2014, 2015. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . .v Trademarks . vi IBM Redbooks promotions . vii Preface . ix Authors. ix Now you can become a published author, too! . .x Comments welcome. xi Stay connected to IBM Redbooks . xi Chapter 1. Introduction. 1 1.1 PowerVP overview . 2 1.2 PowerVP features and benefits. 2 1.3 PowerVP architecture . 4 Chapter 2. Planning and installation . 9 2.1 Planning for PowerVP . 10 2.1.1 PowerVP security considerations . 12 2.2 PowerVP installation . 12 2.2.1 PowerVP installation overview . 13 2.2.2 PowerVP installer on Microsoft Windows systems . 13 2.2.3 Installing PowerVP GUI on AIX or Linux. 27 2.2.4 Installing PowerVP agent manually on IBM i . 30 2.2.5 Installing PowerVP agent on AIX and the VIOS . 31 2.2.6 Installing PowerVP agent on Linux . 34 2.3 Starting and stopping PowerVP . 39 2.4 Upgrading PowerVP agents . 40 2.5 PowerVP SSL configuration .
    [Show full text]
  • Programming the Cell Broadband Engine Examples and Best Practices
    Front cover Draft Document for Review February 15, 2008 4:59 pm SG24-7575-00 Programming the Cell Broadband Engine Examples and Best Practices Practical code development and porting examples included Make the most of SDK 3.0 debug and performance tools Understand and apply different programming models and strategies Abraham Arevalo Ricardo M. Matinata Maharaja Pandian Eitan Peri Kurtis Ruby Francois Thomas Chris Almond ibm.com/redbooks Draft Document for Review February 15, 2008 4:59 pm 7575edno.fm International Technical Support Organization Programming the Cell Broadband Engine: Examples and Best Practices December 2007 SG24-7575-00 7575edno.fm Draft Document for Review February 15, 2008 4:59 pm Note: Before using this information and the product it supports, read the information in “Notices” on page xvii. First Edition (December 2007) This edition applies to Version 3.0 of the IBM Cell Broadband Engine SDK, and the IBM BladeCenter QS-21 platform. © Copyright International Business Machines Corporation 2007. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Draft Document for Review February 15, 2008 4:59 pm 7575TOC.fm Contents Preface . xi The team that wrote this book . xi Acknowledgements . xiii Become a published author . xiv Comments welcome. xv Notices . xvii Trademarks . xviii Part 1. Introduction to the Cell Broadband Engine . 1 Chapter 1. Cell Broadband Engine Overview . 3 1.1 Motivation . 4 1.2 Scaling the three performance-limiting walls. 6 1.2.1 Scaling the power-limitation wall . 6 1.2.2 Scaling the memory-limitation wall .
    [Show full text]
  • Redbooks Paper Bringing PHP to Your IBM Iseries
    David Larson Bryan Logan Redbooks Paper Tim Massaro Heiko Mueller Brian R. Smith Bringing PHP to Your IBM iSeries Server Hypertext Preprocessor (PHP) is a powerful server-side scripting language for the Apache Web server. PHP is popular for its ability to process database information and create dynamic Web pages. Server-side refers to the fact that PHP language statements, which are included directly in your HTML, are processed by the Web server. Scripting language means that PHP is not compiled. Since the results of processing PHP language statements is standard HTML, PHP-generated Web pages are quick to display and are compatible with most all Web browsers and platforms. PHP is for the open source Apache community as Net.Data® is for the IBM® community. To “run” PHP scripts with your HTTP Server (powered by Apache), a PHP engine is required on your IBM ^™ iSeries™ server. The PHP engine is an open source product, so this IBM Redpaper demonstrates the process to download, compile, install, and then configure PHP on your iSeries. It explains how to install versions 4.3.0 and the older version 4.2.2 of PHP. The PHP engine is available both as an Apache module and a CGI-BIN. Support for PHP as a module is not yet available for OS/400®. The step-by-step implementation discussed in this Redpaper involves the CGI version of PHP running in OS/400 Portable Application Solutions Environment (PASE). This allows you to run AIX® binaries directly on an iSeries. It includes the necessary patches for the minor modifications needed to the PHP source code.
    [Show full text]
  • Market-Driven Quality: IBM, Rochester, MN
    --------------1_------------ Midwestern Region Market-Driven Quality: IBM, Rochester, MN Rao J. Tatikonda Building on basic beliefs - respect for the other recommendations during the annual Event Reports individual, the best customer service, and update of five-year strategic plans. Market Driven Quality: 25 excellence in all pursuits - IBM's Baldrige­ 2. Improve the requirements definition pro­ IBM, Rochester, MN winning facility in Rochester, MN embarked on cess. a transformation to market-driven quality Self·Directed Work Teams: 28 3. Implement Six Sigma defect level quality starting in the early 1960s. Now Rochester Basics and Success Factors strategy. IBM Rochester's goal is Six Sigma employees are driving toward defect-free per­ Global Supply Management: 30 by 1994. That means no more than 3.4 formance by 1994, as part of the corporate­ You Can't Be Excellent defects per million units or opportunities. All By Yourself wide effort to qualify the entire company for Specific steps include eliminating manual the national quality award. Multifin Workshop, May 14-15, 32 operations in interpreting specifications, Change, Choice, and Continuous Following are elements of IBM and continuously improving design tools Improvement Rochester's approach to market-driven quality, and techniques to prevent defects early in Tour America 1991: 34 shared during the recent AME workshop. Several the design cycle and to improve cycle Something Special in Wisconsin perfonnance measures are shown in Figure 1. times. Market·Driven Quality Success Factors 4. Create and deploy an Excellence in Educa­ IBM Rochester's market-driven quality tion plan. cycle integrates six critical success factors, with 5.
    [Show full text]
  • High Availability on the AS/400 System a System Manager’S Guide
    Front cover High Availability On the AS/400 System A System Manager’s Guide Tools and solutions to improve your highly available AS/400 system Components for a successful high availability system Hardware options for high availability Redpaper Susan Powers Nick Harris Ellen Dreyer Andersen Sue Baker David Mee ibm.com/redbooks International Technical Support Organization High Availability On the AS/400 System: A System Manager’s Guide June 2001 Take Note! Before using this information and the product it supports, be sure to read the general information in Appendix H, “Special notices” on page 183. First Edition (June 2001) This edition applies to Version 4, Release Number 5 of OS/400 product number 5769-SS1. Comments may be addressed to: IBM Corporation, International Technical Support Organization Dept. JLU Building 107-2 3605 Highway 52N Rochester, Minnesota 55901-7829 When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. © Copyright International Business Machines Corporation 2001. All rights reserved. Note to U.S Government Users - Documentation related to restricted rights - Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp. Contents Preface . ix The team that wrote this Redpaper . ix Comments welcome . xi Part 1. What is high availability? . .1 Chapter 1. Background. .3 1.1 When to consider a high availability solution . .3 1.1.1 What a high availability solution is. .3 1.2 What high availability is. .5 1.2.1 Levels of availability .
    [Show full text]
  • DB2 and PHP Best Practices on IBM I.Key
    DB2 and PHP In Depth on IBM i seidengroup.com Seiden Group and Club Seiden Alan is a leader and expert in PHP on IBM i; leader, Zend’s PHP Toolkit for IBM i; and “Performance guru of PHP on IBM i” Seiden Group is a team of experts available for mentoring/troubleshooting/project advice/development. seidengroup.com, [email protected] Seiden Group 2 DB2 and PHP: Essentials Contact Alan Seiden [email protected] 201-447-2437 www.SeidenGroup.com twitter: @alanseiden Seiden Group 3 DB2 and PHP: Essentials Today’s discussion will include: • Uniqueness of DB2 for IBM i • Which DB2-enabled middleware to use with PHP • Securing your SQL with prepared queries • Connection options for speed and reliability § Persistent connections § Library lists • What’s NEW in ibm_db2 • Connecting from “off the box” • Many other tips Seiden Group 4 DB2 and PHP: Essentials Why learn DB2 best practices? • As chief database on IBM i, DB2 runs these: •Most transaction processing systems •Stored procedures •“XMLSERVICE” Toolkit • Accessible with db2 stored procedures from PHP • DB2 knowledge will help you: •Maximize speed •Reduce CPU usage •Maximize reliability • Avoid unexpected locking and other operational problems Seiden Group 5 DB2 and PHP: Essentials Heart of IBM i is DB2 • DB2 built in § Transaction processing workhorse § Database implemented below operating system level! • IBM i’s “Machine Interface (MI)” between OS and hardware § Journaling, auditing, commitment control very commonly used § Never corrupted • Doesn’t lose data even if knock out power plug
    [Show full text]
  • AS/400 HTTP Server Performance and Capacity Planning
    AS/400 HTTP Server Performance and Capacity Planning Gottfried Schimunek, Erich Noriega, Greg Paswindar, George Weaver International Technical Support Organization http://www.redbooks.ibm.com SG24-5645-00 International Technical Support Organization SG24-5645-00 AS/400 HTTP Server Performance and Capacity Planning January 2000 Take Note! Before using this information and the product it supports, be sure to read the general information in Appendix D, “Special notices” on page 195. First Edition (January 2000) This edition applies to Version 4 Release 4 of OS/400. Comments may be addressed to: IBM Corporation, International Technical Support Organization Dept. JLU Building 107-2 3605 Highway 52N Rochester, Minnesota 55901-7829 When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. © Copyright International Business Machines Corporation 2000. All rights reserved. Note to U.S Government Users - Documentation related to restricted rights - Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp. Contents Figures ......................................................vii Tables .......................................................xi Preface ..................................................... xiii The team that wrote this redbook ......................................xiii Commentswelcome................................................xiv Chapter 1. AS/400 HTTP
    [Show full text]
  • Using DB2 Monitors to Analyze and Improve SQL & Query Performance
    IBM System i™ Session: 440101 (47MA) Using DB2 Monitors To Analyze and Improve SQL & Query Performance Gene Cobb IBM Rochester, MN 8 Copyright IBM Corporation, 2006. All Rights Reserved. i want stress-free IT. This publication may refer to products that are not currently available in your country. IBM makes no commitment to make i want control. available any products referred to herein. i want an i. IBM System i Query Optimization and Execution Feedback V5R4 delivers! Many new and exciting tools for monitoring and analyzing DB2 UDB for iSeries SQL requests and SQL performance 2 i want an i. © 2006 IBM Corporation 1 IBM System i Query Optimization and Execution Feedback V5R4 V5R4 V5R4 Visual Explain Index SQE Plan SQE Cache Advised PlanCache Snapshots Detailed DB Monitor Data SQL request Summarized DB Monitor Query Data Optimization Debug Print SQL Job Log Information Messages Messages 3 i want an i. © 2006 IBM Corporation IBM System i What are the DB2 SQL Performance Monitors? • Integrated tool set used to gather database performance related statistics for SQL-based requests running on the iSeries – i5/OS – Applicable to both batch jobs and interactive work – Only collect information on the DB2 engine processing - does not include the time that it took for the requests to get to the DB2 engine (e.g., JDBC driver processing) • Monitor data dumped into table(s) where it can be queried to help identify and tune performance problem areas – Collected data can be analyzed to look at SQL performance at a global system level, job-level or, specific SQL statement level • Monitor data most useful given a basic understand of DB2 UDB engine and query optimization techniques • Monitor data does not tell you what to do – The science and art of query performance needs to be applied 4 i want an i.
    [Show full text]
  • SQL Procedures, Triggers, and Functions on IBM DB2 for I
    Front cover SQL Procedures, Triggers, and Functions on IBM DB2 for i Jim Bainbridge Hernando Bedoya Rob Bestgen Mike Cain Dan Cruikshank Jim Denton Doug Mack Tom Mckinley Simona Pacchiarini Redbooks International Technical Support Organization SQL Procedures, Triggers, and Functions on IBM DB2 for i April 2016 SG24-8326-00 Note: Before using this information and the product it supports, read the information in “Notices” on page ix. First Edition (April 2016) This edition applies to Version 7, Release 2, of IBM i (product number 5770-SS1). © Copyright International Business Machines Corporation 2016. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . ix Trademarks . .x IBM Redbooks promotions . xi Preface . xiii Authors. xiii Now you can become a published author, too! . xvi Comments welcome. xvi Stay connected to IBM Redbooks . xvi Chapter 1. Introduction to data-centric programming. 1 1.1 Data-centric programming. 2 1.2 Database engineering . 2 Chapter 2. Introduction to SQL Persistent Stored Module . 5 2.1 Introduction . 6 2.2 System requirements and planning. 6 2.3 Structure of an SQL PSM program . 7 2.4 SQL control statements. 8 2.4.1 Assignment statement . 8 2.4.2 Conditional control . 11 2.4.3 Iterative control . 15 2.4.4 Calling procedures . 18 2.4.5 Compound SQL statement . 19 2.5 Dynamic SQL in PSM . 22 2.5.1 DECLARE CURSOR, PREPARE, and OPEN . 23 2.5.2 PREPARE then EXECUTE. 26 2.5.3 EXECUTE IMMEDIATE statement .
    [Show full text]
  • The POWER4 Processor Introduction and Tuning Guide
    Front cover The POWER4 Processor Introduction and Tuning Guide Comprehensive explanation of POWER4 performance Includes code examples and performance measurements How to get the most from the compiler Steve Behling Ron Bell Peter Farrell Holger Holthoff Frank O’Connell Will Weir ibm.com/redbooks International Technical Support Organization The POWER4 Processor Introduction and Tuning Guide November 2001 SG24-7041-00 Take Note! Before using this information and the product it supports, be sure to read the general information in “Special notices” on page 175. First Edition (November 2001) This edition applies to AIX 5L for POWER Version 5.1 (program number 5765-E61), XL Fortran Version 7.1.1 (5765-C10 and 5765-C11) and subsequent releases running on an IBM ^ pSeries POWER4-based server. Unless otherwise noted, all performance values mentioned in this document were measured on a 1.1 GHz machine, then normalized to 1.3 GHz. Note: This book is based on a pre-GA version of a product and may not apply when the product becomes generally available. We recommend that you consult the product documentation or follow-on versions of this redbook for more current information. Comments may be addressed to: IBM Corporation, International Technical Support Organization Dept. JN9B Building 003 Internal Zip 2834 11400 Burnet Road Austin, Texas 78758-3493 When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. © Copyright International Business Machines Corporation 2001. All rights reserved. Note to U.S Government Users – Documentation related to restricted rights – Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp.
    [Show full text]