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

Database partitioning by adding new column without application program change .

IP.com Disclosure Number: IPCOM000016708D
Original Publication Date: 2003-Jul-10
Included in the Prior Art Database: 2003-Jul-10
Document File: 2 page(s) / 17K

Publishing Venue

IBM

Abstract

Disclosed is an idea of how to partition the database without changing application program. When a database is partitioned, partition key column is required. But some databases don't have appropriate partition key column. In this case, "adding a new column with changing program" seems to be normal approach. But when using this new idea, application program does not have to be changed.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 55% of the total text.

Page 1 of 2

Database partitioning by adding new column without application program change .

  (Following explanations are based on IBM DB2 for OS/390 . It seems to be applicable for some other Relational Database. )

1. Purpose and restrictions of database partitioning.

Some databases are partitioned by following reasons. - require more capacity. - need parallel processing.. - minimize backup / recovery time.
- etc.

When a database is partitioned, partition key column is required. Each part range is defined by using this column. But this column should not be updated for performance reason, and steadily increasing field (like timestamp) is not appropriate to partition key column because each part range is not altered dynamically.

2. Normal approach to database partitioning.

Some databases don't have appropriate partition key column. When this type of database is required to partition, the most normal approach is to add new column to define part range. (Although this column is meaningless for application requirement.)

For example: - Second of record inserted time. - "2 figures under" an order serial number. (Next example).

New partition key Order serial number Accept date Status Delivery date

01 02023401 2002/02/03 Delivered 2002/02/13

01 03040501 2003/04/04 Delivered 2003/04/21

02 02048702 2002/05/30 Delivered 2002/06/10

02 03000402 2003/07/13 Waiting to deliver ----

In this case application program must be developed with considering this column.

When first stage of development , program development with considering this column is NOT so difficult. But after program development has finished, this program must be CHANGEd.

=> New development and additional test ( caused by no application requirement) => If new bug is included, program quality is degraded.

=> Database partitioning way without changing program is in great...