IBM Red Brick Warehouse Server Roadmap/Futures Fred Ho

  • 1,102 views
Uploaded on

 

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
1,102
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
7
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • Red Brick Warehouse An embeddable, “channel-ready” data warehouse Simple architecture, high performance and scalability Fast deployment! Low maintenance, easy to install, administer, and use Over 700 installations worldwide What Red Brick is used for? CRM / Marketing / Behavior analysis system Analysis of business activity over time Few DBA resources and/or fast deployment required Replacement of slow-performing warehouse or mart (e.g., Oracle, Sybase, SQL-Server) Red Brick is packaged with analytic applications, e.g.: Ascential WebSuccess - web analytics SPSS CustomerCentric (customer relationship management) Accrue (eCRM) Note: Red Brick Warehouse is currently being sold only through the channel to new customers. Direct sales should lead with DB2 for new customers and new data warehouses at existing customers. For further information on Red Brick Warehouse, see: http://www-3.ibm.com/software/data/informix/redbrick/
  • This chart starts fairly blank but will be very busy before it is done. Before starting let me just come clean on the purpose. The intent here is to convince you of one thing. At IBM, just as at Informix, databases never die, they continue to receive support and enhancement for as long as customers require. We’ll take a little trip through the evolution of database products at Informix and then fill in with how a similar theme developed at IBM. C-ISAM – invented by Informix, standardized by ISO, basic record access library. Support and modern platform availability today. SE – SQL interface (invented and submitted to standards bodies by IBM) added to the record access structure of C-ISAM. Data Portability from C-ISAM was made straightforward. In many cases, customers could use both their C-ISAM applications and new SQL applications against the same data. Support and modern platform availability today. OnLine – step function improvement in availability: online backup/restore, fast recovery and mirroring. SE’s SQL and 4GL connectivity was preserved so applications were highly portable. Data loader provided speedy migration. Support and modern platform availability today. IDS 7 – All the benefits of OnLine taken to a new architecture to leverage modern multi-processor power = performance and scalability. Single queries can be processed n-times as fast (n = # of CPUs). OnLine’s SQL and 4GL connectivity was preserved. Data was migrated in place. Indexes were rebuilt automatically. Support and modern platform availability today. XPS – Intended as the evolution to clusters of the IDS innovation. Extreme, near-linear scalability to MPP and clusters. Biggest obstacle to uptake was that application portability was not preserved – XPS v1 could not do what IDS could do at the time. (chose a DW specialization which left most customers on IDS which continued to be developed separately). Support, enhancement and modern platform availability today. Red Brick – Developed separately as a startup by Ralph Kimball and optimized to do one thing which it does very well – Star Schemas. Everything focused on this which left it very simple to configure and tune. Took into account all aspects of the Star schema based warehouse – load, joins, indexes, build-in analytical functions. Support, enhancement and modern platform availability today. IDS 9 – Back on track regarding natural upgrade and evolution, 100% compatible with IDS 7 but with extensibility and a number of core database enhancements – Ease of Management, more security, Long Ids, Performance and additional SQL compatibility with Industry standards focus. Informix worked very hard to make IDS 9 an easy upgrade from IDS 7 – no data movement, no index rebuild, 100% application portability. Most of the early performance anomolies are corrected and it is very stable. IMS – In case you think Informix invented databases, however, it is important to remember that IBM Research had been innovating for many years before Informix was founded. IBM developed and released IMS in the 70’s. It shipped with the large host computers IBM was shipping at that time. It’s fast and highly reliable heirarchical format has withstood the test of time and it continues to run the backbone of today’s largest financial institutions. IBM continues to provide this customer set with enhancements to IMS on a regular basis. DB2/390 – The relational database was invented to overcome many of the storage and processing inefficiencies of the Heirarchical database. In fact, many predicted that DB2 (IMS being DB1!) would completely replace IMS by the end of the 80’s. DB2 became very popular but never did erase IMS. DB2’s benefits were speed and its use of standardized SQL as a programming language. It has a long legacy of very high availability and runs on some of the world’s most powerful computers. DB2/UDB – IBM’s strategy for open systems was and remains to recognize that the IT world of major enterprises is made up of data in more than one place. Therefore, early in its evolution, support for distributed and heterogeneous data query was engineered into products like Data Joiner. This concept embellished by leveraging the standard of XML forms the core of the continuing strategy towards Information Integration. Already as capable as any of the other database vendors at the basics of storing and retrieving structured and unstructured data, ongoing DB2/UDB investment focuses on the really tough problems of providing a common access interface to all of your enterprise data. DB2 (Next) – The arrowhead strategy of Informix continues and grows to include DB2/UDB. Experienced engineers in Toronto from DB2, in Portland from Informix in San Jose from both sides are working on integrating the most compelling IDS, XPS and Red Brick features into new versions of DB2 to provide a natural upgrade path from each in the near future. However, a serious infusion of brand new database innovation is occurring on DB2/UDB simultaneously that is sure to be interesting to both current DB2 and Informix users, as well as a large portion of the other database users – many of whom are locked into arrogant business practices or closed solutions. In later slides, we show DB2’s new XML support involving standarization of Xquery, Information Integration, and continuing the SMART initiatives.
  • “ Is IBM going to force me off of Informix and on to DB2?” Unequivocally, “NO!”. Despite what you may have heard from our competitors, there will be no forced migrations. You can keep your current applications on Informix for as long as you want to. There isn’t a lot of benefit from taking a tuned, working application to another database platform unless there are extenuating circumstances that require it. Moving databases is a very difficult proposition and there must be a very clear value advantage presented before you undertake that. Our preference would be for customers to hear out the DB2 value proposition. We think you’ll like what you hear. So you’ll be offered opportunities to consider DB2 for new applications and we invite you to check them out, but please, rest assured that there will be ongoing support for Informix products for many, many years. Take IMS as an example. Built in 1968, superseded by DB2-mainframe in the mid-80’s, yet regular quality and feature releases get shipped on regular intervals and the customers are thrilled with the stability and performance Later in this presentation, we will discuss our plans for bringing key Informix functionality into DB2.

Transcript

  • 1. IBM Red Brick Warehouse Server Roadmap/Futures Fred Ho & Cindy Fung Software Development Managers Information Management Solutions
  • 2. Topics
    • Red Brick Update
      • Red Brick as part of IBM
      • Red Brick Product Roadmap
      • Red Brick Versions 6.2 and 6.3 Overview
      • Red Brick Gold Bundles
      • Summary
    • Red Brick and DB2 Information Integration
    • 6.3 Features Detail
    • Future considerations
    • Summary
  • 3. Quick update on Red Brick @ IBM
    • Loyalty to Red Brick Warehouse Server
      • Continued strong endorsement by customers
      • Continued investment & support by IBM
    • Product roadmap
      • Maintained release timelines as pre-acquisition days
      • Shipped one major enhancement release (v6.2) & several maintenance releases
      • Next feature release is on target
    • Red Brick team
      • Integrated into IBM Data Management and BI group at SVL
      • Retention still very high
    • Red Brick partnerships
      • Key part of the acquisition
      • Strong retention of partners
  • 4.
    • 2002
    2003 Integrated Analytics 2004 Interoperability Performance, Usability IBM Red Brick Warehouse Roadmap High Performance, Easy to Administer Data Mart Engine 2005 Red Brick v6.2 Red Brick v6.3
    • Target: (1H2004)
    • DB2 BI tools integration
    • Performance Improvements to STARJoin and TARGETJoin
    • Dynamic Smart Scan
    • Self Tuning TMU Block Cache Surrogate Key Generation &
    • Expression support in TMU
    • Improve performance of aggregations,deletes, table scans, etc.
    • Others .....
    • GA’ed Oct. ‘02
    • ANSI SQL/OLAP functions
    • Integrated Backup/Restore
    • Query/Load Performance
    • Load/Export data in XML
    • Performance monitor
    • Locally segmented indexes
    • Others ….
    Red Brick v6.4
    • In Planning: (2H2005)
    • Increased parallelism for query performance and loader support
    • Additional platform support
    • Improved diagnostics
  • 5.
    • SQL/OLAP
    • Vista Query Rewrite Extensions
    • Query Performance Monitor
    • Locally Segmented Index
    • Backup & Restore Facility
    • XML Data Load/Unload
    • Remote Load TMU
    • System Catalog Improvements
    • Upgrade to 6.20 (32 bit to 64 bit)
    • Segment DDL Enhancements
    • Connectivity (ODBC/JDBC) Enhancements
    GA - 10/1/02 in Passport Advantage Red Brick v6.2 Content – Available today Majority of customers have migrated to v6.2
  • 6.
    • Major Performance Improvements
      • Dynamic Smartscan
      • Memory mapping of dimension index/tables for STARjoin performance
      • Target Join improvements for local index
      • Optimizer hints to specify STARindex for fact-to-fact joins
      • Table Management Utility (TMU) Memory Tuning for non-optimized loads
    • Major Usability Improvements
      • Alter Table with Working Segment
      • Additional Expression support (e.g. conditional IF's) in the Loader
      • Additional SQL/OLAP functions, e.g. Round, Median
      • Shrink System Catalog Utility
      • Allow 3GB Address Space on Windows Platform
      • Delimiter enhancements in Loading and Exporting
    • Port and OS Versions Upgrade
      • Support HP Itanium Product Family (IPF) (64-bit)
      • Upgrades for AIX v5.2, SUN Solaris 9, DEC Tru64 5.1A
    Planned v6.3 - Themes and Content GA – 1H2004 in Passport Advantage Red Brick v6.3 Themes and Content
  • 7. IBM, Informix & Red Brick Database evolution C-ISAM Indexed Record access SE SQL Interface, Stored Procedures Online Available, Distributed, Performance IDS 7 Scalable, Parallel ’ 70s ’80 ’85 ’90 ’95 ’00 ’05 …… IMS – Hierarchical, Very Fast, Available DB2/390 - SQL Interface, Stored Procedures, Available DB2/UDB - Open, Parallel, Available, Federated, XPS – DW on MPP, Clusters Red Brick – Star Schema IDS 9 Extensible, Usable, Secure DB2 Arrowhead – SMART, Information Integration Includes best of IDS, XPS, Red Brick & DB2 30 years of Innovation and Investment protection
  • 8.
    • Can I stay on Red Brick or will IBM make me move to DB2?
    • Our Philosophy
      • "Moves anywhere are difficult. Move only if the result is a recognizable value advantage for you”
    • Our Promise
      • "We'll continue to support the Red Brick product line for as long as customers require"
    • Our Proof
      • "100's of IMS* customers still receive regular updates to a product originally released in 1968" (IMS is a mainframe, hierarchical database, the backbone of the world's financial systems)
  • 9. Red Brick Customer Status
    • IBM’s goal with Red Brick is to continue to sell to and support our customers via direct sales and partner sales world-wide
    • We have maintained very strong customer loyalty
      • Existing customers growing their Red Brick environments
    • Our customers are happy with Red Brick, the IBM Data Management strategy and are looking into other DB2 products such as: DB2 Warehouse Manager, DB2 Intelligent Miner, DB2 Information Integrator, etc.
  • 10. Customer Facing Events
    • European Red Brick Users’ Group Meeting
      • Sept. 5 th , 2003 in Milan, Italy
    • IBM Data Management Technical Conference from
      • Oct 27 – 31 2003 in Las Vegas
      • Numerous Technical sessions on Red Brick by senior members of the Red Brick team
      • Key Red Brick customer presentations
      • Joint DB2 and Red Brick sessions also included
    • Red Brick v6.3 Beta Program to start in Oct 2003
      • Early access to the new features
      • Ability to work closely w/ R&D to help influence the quality of the release
      • Will work with other BI vendors to test and support Red Brick v6.3
  • 11. Red Brick Integration into DB2
    • Introduce key Red Brick technologies over next few years into DB2
      • Lead development of next generation DB2 star join algorithm
      • Participate in the design of other core technology projects
        • Data partitioning
        • Load performance and function
        • MQT (Materialized Query Table) enhancements
      • Champion other DB2 SQL extensions
      • Assist definition of “ease of administration” requirements
        • Synchronize with SMART team
    • Provide interoperability support with other DB2 products
      • DB2 Warehouse Manager
      • DB2 Information Integrator
      • Query Monitoring Facility (QMF for Windows)
    • Provide integration with System and Storage Management
      • Tivoli TSM
  • 12. GOLD BUNDLES
    • WHAT IS A GOLD BUNDLE?
      • Product offering designed to offer a sense of "one" company
      • "Customer Choice" Database License
      • Customer can choose database platform as needs dictate, using same license for different products
      • Single database license offering customers a choice of IBM DM products (i.e. Informix, Red Brick, DB2)
  • 13. RED BRICK GOLD BUNDLES
    • Red Brick Analytic Bundle - Enterprises contains:
      • IBM Red Brick Warehouse Server v6.2
      • IBM DB2 ESE v8.1
      • IBM DB2 Developers Edition v8.1 (5 users)
      • IBM DB2 Warehouse Manager v8.1
    • Red Brick Analytic Bundle - SMB contains:
      • IBM Red Brick Warehouse Server Work Group Edition v6.20
      • DB2 WorkGroup Server Unlimited Edition WSE v8.1
      • DB2 Universal Developers Edition v8.1 (One user only)
  • 14. DB2 Information Integrator V8.1 & Red Brick Warehouse Server
  • 15. DB2 Information Integrator
    • Introducing new integration software : DB2 Information Integrator
      • DB2 Information Integrator 8.1
      • DB2 Information Integrator for Content 8.2
    • Announcing beta availability
      • Access beta through IBM client representative
    • Key business value:
      • Optimize IT investments given more choice in data access
      • Integrate data with better productivity and application efficiency
      • Gain more return from existing assets
  • 16. DB2 Information Integrator : Value for Red Brick
    • Key business value:
      • Optimize IT investments given more choice in data access
      • Integrate data with better productivity and application efficiency
      • Gain more return from existing assets
    • Data Federation (leave your data where it is)
      • Create new applications via DB2 that integrate data stored in Red Brick with data from other sources such as DB2, Oracle, Sybase, SQL Server, Teradata, XML files, Flat files, Message Queues, Web Services, ODBC databases…
      • Enable existing DB2 applications that use DB2/UDB APIs, e.g. ODBC/JDBC/ESQL to access data in Red Brick
        • A single API for access to both Red Brick or Informix or DB2 or Oracle or…
  • 17. Scenario: Integrate Red Brick with DB2 UDB
    • Your Value
      • Integrate Red Brick data marts seamlessly with DB2 UDB, Informix, Oracle or Flat files
      • Enable a unified view of data across multiple Red Brick marts combined with data in DB2 UDB
    • What You can do
      • Red Brick + DB2 II (Standard Edition)
        • Includes a “limited use” license that allows you to federate Red Brick data marts with DB2 UDB and Informix databases (XPS and IDS)
        • Additional data sources, e.g. Oracle, require a full license
  • 18. Scenario: Enable Third Party App Support
    • Your Value
      • Want to use packaged applications (e.g. SAS Campaign Manager) but application does not support Red Brick natively
    • What You can do
      • DB2 Information Integrator SE
      • Build the infrastructure to enable access of Red Brick data via DB2 II to the SAS Campaign Manager
  • 19. IBM Red Brick Warehouse Server 6.3 Features
  • 20. 6.3 Features
    • Major Performance Improvements
      • Dynamic Smartscan
      • Memory mapping of dimension index/tables for STARjoin
      • TARGETjoin improvements for local index
      • Optimizer hints to specify STARindex for fact-to-fact STARjoin
      • Table Management Utility (TMU) Memory Tuning
    • Major Usability Improvements
      • Additional SQL/OLAP functions
      • Expression support in the Loader
      • XML Improvements in Loader
      • Compact System Catalog Utility
  • 21. 6.3 Features
    • Major Usability Improvements – cont’d
      • Allow 3GB Address Space on Windows Platform
      • Delimiter enhancements in Loading and Exporting
      • Alter Table with Working Segment
      • Interoperability with DB2 products
    • System Port
      • Support HP Itanium Product Family (IPF)
    • OS Versions Upgrade
      • AIX v5.2
      • Sun Solaris 9
      • HP-UX IPF 11i
      • Windows32 on Server 2003
  • 22. Dynamic SmartScan
    • Additional queries could be considered for SmartScan segment elimination
    • Include constraints not on the segment column and the fact table is segmented by the referenced foreign key
      • Currently, could eliminate segments only with constraints on the segmenting column
    • Dynamic segment elimination is possible:
      • When we can evaluate the constraints in prelim plans on dimension-to-fact join, and
      • Strategizer chooses Table-Scan OR locally indexed Target-Join plan on the segmented fact table
    • Improve selectivity estimates to consider outcome of segment elimination, both static and dynamic
      • more accurate dynamic selection of STARjoin plan choices
  • 23. Dynamic Segment Elimination Example
    • Assume, “Sales” as a Fact table that is segmented by a foreign key “perkey”.
    • RISQL> Select Sum(Dollars) From Sales, Period
        • Where Sales.perkey = Period.perkey And
        • Period.date >= ’01-01-01’ And
        • Period.date <= ’12-31-01’ ;
    • Above mentioned query could potentially eliminate unwanted segments from “Sales” table if it chooses Table Scan OR local target-join on “Sales”.
  • 24. MMAP Dimension Table/Index
    • Reduce CPU overhead and I/O system calls by mmap dimension indexes and tables into shared memory
    • Apply to STARjoin/TARGETjoin/tablescan plans
      • Typically contain Btree-1-1-Match (B11M) and Functional Join operators to perform joins and row fetches to dimension tables
    • High benefit for queries with large number of rows produced from join(s) below the B11M and Functional Join operators
      • Mmap could potentially improve performance of
        • B11M when mmap corresponding dimension primary index
        • Functional Join when mmap corresponding table
        • Multiple queries/users sharing the single copy in shared memory
  • 25. TARGETjoin Performance
    • Improve performance of TARGETjoin
      • Particularly for local indexes
      • More consistent performance between tightly and loosely constraints
      • More efficient index access for TARGETjoin and Scan operators
    • Local Index TARGETjoin improvement from 0 - 500%
      • Biggest speedup on poorly performing joins
      • Particularly helps loose constraints on large dimensions
      • Preliminary test results approaching STARjoin performance in about 50%
    • Allow single column B-Tree indexes in TARGETjoin
      • Consider B-Tree index on foreign keys with very large dimensions
      • Not always a win, particularly with loosely constraints on large dimensions
      • Could be a big win with tight constraints
  • 26. Optimizer Hints
    • STAR indexes can be specified for queries on a per table basis
      • Must be careful when overriding optimizer selection
    • A specific STAR index
    • SET STAR INDEX AVAILABILITY (TABLE1_STAR_IX1) FOR TABLE1;
    • Multiple STAR indexes
    • SET STAR INDEX AVAILABILITY (TABLE1_STAR_IX1, TABLE1_STAR_IX2) FOR TABLE1;
    • STAR indexes on a per multi-fact table STARjoin basis
    • SET STAR INDEX AVAILABILITY (TABLE1_STAR_IX1) FOR TABLE1 WHEN STARJOIN BETWEEN (TABLE1, TABLE2);
    • SET STAR INDEX AVAILABILITY (TABLE1_STAR_IX2) FOR TABLE1 WHEN STARJOIN BETWEEN (TABLE1, TABLE3);
  • 27. Optimizer Hints
    • STARjoin and TARGETjoin thresholds can be specified on a per table basis
    • SET STARJOIN THRESHOLD 20 FOR TABLE1;
    • SET STARJOIN THRESHOLD 5 FOR TABLE2;
    • SET TARGETJOIN THRESHOLD 40 FOR TABLE 1;
    • SET TARGETJOIN THRESHOLD 10 FOR TABLE2;
  • 28. TMU Memory Tuning
    • Better control over TMU memory resource usage
    • Allows TMU buffer memory to be tuned according to the load job
    • Introduces memory balancing between parallel loader tasks
    • Quickly allocate large amounts of buffer memory
    • Prevents excessive use of system memory by defining a maximum amount of buffer memory that could be used by the load job
    • Reports on TMU buffer usage: fine tuning for repetitive load jobs
  • 29. TMU Memory Tuning
    • Tuning rule of thumb: more logical I/O requires more buffers
    • Syntax:
      • SET TMU MAX BUFFERS number_of_blocks
      • SET TMU CONVERSION BUFFER PERCENT p
      • SET TMU OUTPUT BUFFER PERCENT p
      • SET TMU INDEX BUFFER PERCENT p
    • Recommend using new tunables over SET TMU BUFFERS approach
  • 30. More SQL/OLAP Functions
    • Distribution Functions
    • CUME_DIST
    • PERCENT_RANK
    • Inverse Distribution Functions (Median)
    • PERCENTILE_CONT
    • PERCENTILE_DISC
    • Scalar function
    • ROUND
  • 31. Distribution Functions
    • CUME_DIST() computes the position of specified row value relative to the set of values
      • (# of values equal to or less than x) / (total # of values)
    • PERCENT_RANK() returns the percent rank of a value relative to a group of values
      • (rank of row in partition –1) / (# of rows in partition –1)
    • Example
    0.75 0.33 220,000 1 1 230,000 0.75 0.33 220,000 0.25 0 100,000 Cume_dist Percent_rank Price
  • 32. Inverse Distribution Functions
    • Answers question such as “What is the median (50 th percentile) value of my data?”
    • Require a sort specification and a parameter that takes a value between 0 and 1
    • Use the new WITHIN GROUP clause to specify the data ordering
    • Example
      • Select Area, Price,
      • PERCENTILE_CONT(0.5) WITHIN GROUP (Order by Price) OVER (Partition by Area) as Median_cont,
      • PERCENTILE_DIST(0.5) WITHIN GROUP (Order by Price) OVER (Partition By Area) as Median_disc
      • From Homes;
  • 33. ROUND() scalar function
    • ROUND() returns rounded number to the integer places left or right of the decimal point
    • Examples
      • ROUND (864.827, 2) = 864.830
      • ROUND (864.827, 1) = 864.800
      • ROUND (864.827, 0) = 865.000
      • ROUND (864.827, -1) = 860.000
      • ROUND (864.827, -2) = 900.000
      • ROUND (864.827, -3) = 1000.000
  • 34. Expression Support in Loader
    • Input data can now be modified while being loaded to a table
    • Basic arithmetic operations now supported
    • Modification also possible based on conditions
    • A pseudo column can now be assigned to a target column
    • Multiple conditions now possible in ACCEPT/REJECT clause with some limitations
    • Highly requested functionality
    • More integrated with the server than ETL tools
  • 35. Expression Support in Loader
    • Syntax: (snippets from TMU control file)
    • Arithmetic expressions:
    • $A POSITION(2) INTEGER EXTERNAL(10),
    • ColA ($A + 5)/2
    • Conditions:
    • $A POSITION(2) INTEGER EXTERNAL(10),
    • ColB CASE WHEN $A > 5 THEN $A+3
    • WHEN $A = 5 THEN $A-1
    • ELSE $A+1
  • 36. Expression Support in Loader
    • Pseudo column assignment
    • $A POSITION(2) INTEGER EXTERNAL(10),
    • ColC $A
    • ACCEPT/REJECT clause
    • ACCEPT ($A > 5 AND $B < 10) OR
    • ($C = 15)
    • Limitation:
    • If real columns are used, then just a single condition is allowed. With pseudo columns multiple conditions are allowed (example above)
  • 37. XML Improvements in Loader
    • Extends TMU and SQL Export functionality to provide additional XML support
      • XML multiple namespaces support
      • Export generates default namespace
    • Upgrade to the IBM XML4C v5.x parser
      • key performance enhancements as well as critical fixes over 6.2 Xerces version
      • Seamless upgrade to new parser
  • 38. Compact System Catalog
    • Compacts free space within system catalog
      • Occurs when objects are freed but not at the end of the catalog
    • Extension of System Catalog enhancement in 6.2 where free space is released at the end of the system catalog
    • Rb_syscompact
      • Does the compaction
      • Requires DBA privilege
      • Creates a backup file
      • Checks for catalog sanity before compaction
  • 39. 3GB Address Space on Windows
    • Extend beyond 32-bit memory access limit
    • Increase virtual address space from 2GB to 3GB
    • Feature Advantages
      • More data can be cached in physical memory
      • Greater scalability and performance
    • Supported on
      • 32-bit versions of the Windows® 2000 Advanced Server
      • 32-bit versions of Windows.NET Server
    • Enabled on executables: rb_tmu.exe, rb_ptmu.exe, rbw.exe, rbwtest.exe and risqltty.exe
  • 40. Loading with Multiple Characters Separator
    • Apply to loading and exporting in delimited format
    • new load format clause syntax:
      • format separated by ‘ <separator> ’ [ enclosed by ‘<string delimiter>’ ]
    • Separator may consist of 1 to 10 characters
      • may be composed of single or multi-byte characters
    • Feature Advantages:
      • Data generated by other ETL tools that use multiple characters separator could be loaded directly without modification
      • Data containing separator string will be loaded correctly as long as the data is enclosed within the string delimiter
  • 41. Export with String Delimiter Support
    • Adds delimiter support to enclose a string
    • New export command syntax:
    • export to ‘xxx’ format delimited [by ‘<export delimiter>’ ] [enclosed by ‘<string delimiter>’ ] (<select query>);
    • Export delimiter and string delimiter must be one character
      • may be composed of single or multi-byte character
    • Feature Advantages:
      • May specify a different export delimiter for each export command
      • Export data may be directly loaded back into a database using the loader
      • Export delimiter can be part of the data content when string delimiter encloses the data
  • 42. ALTER TABLE Using a Working Segment
    • Provides more reliable recoverability of failed alter operations than existing alter table IN_PLACE
    • Working segment can be reused after the alter operation is over
    • The table is still altered “in place”
    • Syntax:
      • ALTER TABLE <table_name> [ADD | DROP] COLUMN
      • IN_PLACE [USING <segment_name>]
    • New feature is strongly recommended over IN_PLACE alter
  • 43. ALTER TABLE enhancements
    • Much requested feature
    • Combines nominal space requirements of IN_PLACE alter with reliable recovery characteristic of alter in other segments
    • As a table segment is altered, its original contents are temporarily stored in a standard, user-defined segment (a ‘working segment’)
    • If the alter fails (e.g. due to a full disk), original contents of the table segment are available in the working segment for the alter to be resumed and completed successfully
    • Additional disk space required for the working segment is only as much as the largest segment of the table
  • 44. HP-Itanium Porting Project
    • A native port, not architectural emulation
      • Yields high performance by directly taking advantage of Itanium’s architecture
    • No need to convert data
      • Red Brick databases created on PA-RISC will be fully compatible with Red Brick on HP-Itanium
    • Currently, no vendors plan to support XBSA Backup/Restore interface on HP-Itanium
      • BAR to files or UNIX tapes
  • 45. DB2 Products that support Red Brick currently
    • DataJoiner Version 2.1.1 Works with ODBC wrapper. See http://www7b.boulder.ibm.com/dmdd/zones/informix/library/techarticle/0302rumsby/0302rumsby.html for more info on how to use DataJoiner with Red Brick
    • Warehouse Manager
      • DB2 8.1 FP2
      • See Warehouse Manager document for more information
    • QMF for Windows (ODBC only)
    • Tivoli Storage Manager
  • 46. Future DB2 Interoperability Options
    • Information Integrator
      • Planned for beta in late August
      • GA in November 2003
    • Intelligent Miner for Data
      • Under consideration
  • 47. Features Being Considered Beyond v6.3
  • 48.
    • Features Being Considered
    • Windows-64 Support
    • Improved Query Parallelism
      • Parallel Sort/Improved Order-By
      • Starjoin performance
      • Incremental Maintenance speedup for Vista
    • Partition Parallel Loader
    • Backup/Restore Performance
      • Compression
      • Pipeline parallelism
    • Better Diagnostics
      • Packaged diagnostics of memory, stack, version log dumps
  • 49. Red Brick Futures
    • IBM committed to supporting Red Brick for the forseeable future
    • DB2 is the flagship DM product.
    • Red Brick features being integrated into DB2 over time.
    • Red Brick feature release approximately every 18 months
    • Channel/partners remains a key play for IBM
    Summary:
  • 50. Questions ?