Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Partitioning Key Advisor

IP.com Disclosure Number: IPCOM000013677D
Original Publication Date: 2000-May-01
Included in the Prior Art Database: 2003-Jun-18
Document File: 1 page(s) / 54K

Publishing Venue

IBM

Abstract

A new tool is disclosed to help database licensees moving from a single partition environment to multiple partition environment. Currently, a database licensee (with a serial or single node license) intending to move to distributed multiple partitions needs to buy a multiple partition license and add partitioning keys to all existing tables. DB2 currently imposes a rule: "Any unique or primary key constraint defined on the table must be a superset of the partitioning key". Thus, the customer will need to manually find at least one column common to each unique key (including primary key) of each table and create partitioning key for each table based on the subset. The new tool which will go through all tables and find this subset or closest subset of columns. The tool will return each table name along with its recommendation on the selection of the partitioning key. If a column appears in all key constraints, it will certainly be recommended as part of partitioning key. If there is no column that appears in all key constraints, the column with the highest occurrence in all key constraints will be recommended along with the name of the constraint that does not include this column. Thus, a database licensee could choose to add the column to the constraint "missing that column" and used the column as partitioning key. For a table that already has a partitioning key defined, this tool will indicate that partitioning key already defined. Pseudo-code Logic: 1. connect to database

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 62% of the total text.

Page 1 of 1

Partitioning Key Advisor

  A new tool is disclosed to help database licensees moving from a single partition environment to multiple partition environment. Currently, a database licensee (with a serial or single node license) intending to move to distributed multiple partitions needs to buy a multiple partition license and add partitioning keys to all existing tables. DB2 currently imposes a rule: "Any unique or primary key constraint defined on the table must be a superset of the partitioning key". Thus, the customer will need to manually find at least one column common to each unique key (including primary key) of each table and create partitioning key for each table based on the subset.

  The new tool which will go through all tables and find this subset or closest subset of columns. The tool will return each table name along with its recommendation on the selection of the partitioning key. If a column appears in all key constraints, it will certainly be recommended as part of partitioning key. If there is no column that appears in all key constraints, the column with the highest occurrence in all key constraints will be recommended along with the name of the constraint that does not include this column. Thus, a database licensee could choose to add the column to the constraint "missing that column" and used the column as partitioning key. For a table that already has a partitioning key defined, this tool will indicate that partitioning key already defined.

Pseudo...