Browse Prior Art Database

The SQLDIBS File

IP.com Disclosure Number: IPCOM000110083D
Original Publication Date: 1992-Oct-01
Included in the Prior Art Database: 2005-Mar-25
Document File: 2 page(s) / 66K

Publishing Venue

IBM

Related People

Buquoi, GH: AUTHOR [+4]

Abstract

A method is described to prevent a user from spanning table objects from different databases into the same target directories.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

The SQLDIBS File

       A method is described to prevent a user from spanning
table objects from different databases into the same target
directories.

      When a table object is spanned into multiple directories, the
same physical file name is used for the table object in each
directory.  For example, the user wishes to span table A which is
located in the main database subdirectory in the file, SQL00018.DAT.
The user specifies 2 target directories, D:\TABLES and E:\TABLES.

      After the span:
          D:\TABLES contains a file called SQL000018.DAT (table A)
          E:\TABLES contains a file called SQL000018.DAT (table A)

      This scheme works as long as the user has only 1 database.  If
the user has more than 1 database and attempts to span tables from
both databases into the same target directories, there is a large
potential for file name conflicts.  For example, the user also wishes
to span table B which belongs to a different database than table A,
but is also located in the file SQL00018.DAT.  When spanning table B,
if one of the same target directories is specified that was used when
spanning table A, the table B file would replace the table A file in
that target directory.  The user spans table B specifying 2 target
directories, D:\TABLES and E:\NEWSTUFF.

      After the span:
          D:\TABLES contains a file called SQL000018.DAT (table B)
          E:\TABLES contains a file called SQL000018.DAT (table A)
          E:\TABLES contains a file called SQL000018.DAT (table B)

      How do we prevent the user from spanning table objects from
different databases...