Browse Prior Art Database

Rename Database

IP.com Disclosure Number: IPCOM000107945D
Original Publication Date: 1992-Apr-01
Included in the Prior Art Database: 2005-Mar-22
Document File: 2 page(s) / 52K

Publishing Venue

IBM

Related People

Devany, EP: AUTHOR [+3]

Abstract

This article describes a method for renaming a database to aid network administrators in managing a network containing databases.

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

Rename Database

       This article describes a method for renaming a database
to aid network administrators in managing a network containing
databases.

      The Database Manager is a product designed to meet the needs of
growing customers.  These customers may start out with standalone
databases and grow to putting these databases on a LAN in order to
share the database. Ultimately, they start to combine LANs and share
data across the LANs.

      When the databases are standalone, there is probably little
thought given as to what the database name should be. For example, DB
is a common name.  When these databases are placed on a LAN, there
must be some way of distinguishing them from one another.  Using
ALIAS is one concept which has been used.  However, this should be
used as an exception, not a rule.  Generally, it is desirable to have
unique names in a network.  A function is needed to change existing
names in order to make them unique.  Renaming existing databases will
aid network administrators or application programmers in managing the
database names in a network or on individual workstations.

      To accomplish this, the Database Manager must provide an API
that has a specification for Oldname and Newname. When this API is
coded, the Database Manager will change all references in the System
Database Directory and Volume Database Directory from the Oldname to
the Newname, as shown in the following example:
       Example:   Renami...