JPH0561737A - Validity term managing system for data base object and data base user - Google Patents

Abstract

PURPOSE:To automatically erase the registration of expired object or a user by managing the term of validity of the data base object and the data base user. CONSTITUTION:A relational data base management system (RDBMS) 15 refers to a user management table 14 according to a log-in request from the user and when the user has the validity, it is investigated whether the term of validity is expired or not based on the term of validity set to the table 14 corresponding to the user name. When the term of validity is expired, the registration of the user is erased. When data base access is requested from the user, the RDBMS 15 refers to an object management table 13 and when the object at the destination of access has the term of validity, it is investigated whether the term validity is expired or not based on the term of validity set to the table 13 corresponding to the data base name. When the term of validity is expired, the object is erased.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a database object suitable for use in a relational database system and a database user expiration date management system.

[0002]

2. Description of the Related Art Generally, in a database system, for example, a relational database system, database objects such as tables and indexes are managed by a data dictionary owned by a relational database management system. With this relational database system database management, when a database user (database user) creates a database object, that database object exists unless the user who created the object explicitly deletes it from the data dictionary. And managed.

Also, regarding database users,
Once registered in the data dictionary by the database administrator, it exists and is dictionary managed unless the database administrator is explicitly removed from the data dictionary.

[0004]

As described above, conventionally, a database object once created or a registered database user exists unless the user who created the database object or the database administrator takes a deletion procedure. And managed.

Therefore, a database object (for example, a table) that is known to be unnecessary later is created, or a database user who is known to cancel registration later is registered. In this case, it was necessary to delete the resource when it was no longer needed, in order not to waste resources. However, in reality, there is a problem in that deletion is often forgotten and effective use of resources cannot be achieved.

The present invention has been made in view of the above circumstances, and an object thereof is to manage expiration dates of temporarily used database objects and temporarily used database users, and Database objects and database objects that can be automatically deleted from objects and database user registrations
The purpose is to provide a user expiration date management method.

[0007]

The present invention provides a first method for setting the expiration date of various database objects.
Expiration date setting means (first table), second expiration date setting means (second table) for setting the expiration date of each database user, and the first and second
Based on the setting contents of the table of, the management means for managing the expiration date of each database object and each database user is provided, and the registration of the expired database object and database user is automatically deleted. It is characterized by doing so.

[0008]

According to the above construction, for a database object that is known to be unnecessary later, the period when it is no longer needed is set as the expiration date and set in the first table when the object is created. Database that you know in advance that you will cancel the registration later.
For the user, the scheduled cancellation time is set as the expiration date and is set in the second table when the user is registered, so that the management unit can perform various operations based on the setting contents of the first table and the second table. Since the expiration date of the database object and each database user is managed, the registration of the expired database object and database user can be automatically deleted.

[0009]

1 is a block diagram showing an embodiment of a database system to which the present invention is applied. In FIG. 1, 10 is a host device, and 20 is a terminal connected to the host device 10.

The host device 10 has, for example, a database (relational database) 11 in which various relational database objects are stored, and a data dictionary 12 for managing the database 11.

FIG. 1 shows that the database 11 stores tables (database objects) TA1 and TA2 owned by a user (database user) A and tables TB1 to TB4 owned by a user B. ing. Here, of the tables TA1 and TA2, the shaded table TA2 is temporarily used. It is also assumed that, of the users A and B, the user B, which is shaded (owns the tables TB1 to TB4), is temporarily used (registered).

The data dictionary 12 includes a table (hereinafter referred to as an object management table) 13 for managing the expiration dates of various database objects (hereinafter referred to as DB objects), and an expiration date management for each database user. A table (hereinafter referred to as a user management table) 14 is included.

In the object management table 13, as shown in FIG. 2, the names (DB object names) of all DB objects on the database 11 are stored.
The name of the user who created the object and the object management information including the expiration date indicating when the object is no longer needed are set and registered. Note that it is not necessary to set an expiration date for objects that do not have an expiration date.

Therefore, in the example of the database 11 of FIG. 1, for the table TA1, for example, only the created user name is set corresponding to the object name, and the expiration date is not set. On the other hand, in the table TA2, the created user name and the expiration date are set in correspondence with the object name. The table TB1 owned by user B
As for ~ TB4, since the user B himself / herself is managed with a time limit, it is meaningless to be managed with a time limit beyond that time limit.

Further, in the user management table 14 (each entry thereof), as shown in FIG. 3, for all users (database users) who can use the database 11, their names (user names) and their user names. User management information including a registration expiration date is set and registered. Note that it is not necessary to set an expiration date for users who do not have an expiration date.

Referring again to FIG. 1, the host device 10 also has a relational database management system (hereinafter referred to as RDBMS) 15. RDBM
S15 is a well-known database management (relational
Database management), and data dictionary 12
The expiration dates of DB objects and users (database users) are managed based on (the object management table 13 and the user management table 14 therein). The host device 10 further includes the RDBMS1
5 is located between the terminal 5 and the terminal 20 and has an interface 16 for conversation with the user via the terminal 20.

Next, the operation of one embodiment of the present invention will be described with reference to FIG.
This will be described with reference to the flowchart in FIG. First, R provided in the host device 10 of the database system of FIG.
When starting the database, the DBMS 15 refers to the object management table 13 and the user management table 14 in the data dictionary 12, and has already expired for each object (DB object) or user (database user) created and registered with a deadline. It is checked whether or not (step S1).

If the expired object or user exists, the RDBMS 15 performs a process of deleting the registration (step S2). That is, RDBMS15
Deletes the expired object from the database 11 if it exists. this is,
It is realized by deleting the object name from the object management table 13. Similarly, if an expired user exists, the RDBMS 15 deletes the user name from the user management table 14, and further searches and deletes all the DB objects created by the user from the object management table 13.

Here, it is assumed that after the database is activated, the user operates the terminal 20 to input a request for logging in to the database system. This login request is sent to the RD via the interface 16 of the host device 10.
The BMS 15 is notified.

The RDBMS 15 is a user management table 1
4, when the user who requested the login is registered with a time limit, the expiration date and the current date are compared to check whether the user has already expired (step S3, S4).

If the login request source user has expired, the RDBMS 15 returns an error to that effect to the terminal 20 via the interface 16, and the user name of the login request source user determined to have expired further. Is deleted from the user management table 14, and all DB objects created by the user are searched and deleted from the object management table 13 (step S
5).

On the other hand, if the login request source user is registered without a time limit, or if the user who has registered with a time limit is still within the expiration date, the RDBMS
15 permits the login request. Of course, a login request from a user who is not registered in the user management table 14 cannot be accepted.

Now, it is assumed that the user who has received the login request operates the terminal 20 and inputs a database access command for accessing the DB object in the database 11.

Upon receiving the database access command from the terminal 20, the RDBMS 15 refers to the object management table 13 and, if the access target DB object designated by the command is registered with a time limit, sets the expiration date and time. Compare the current date, then D
It is checked whether the B object has already expired (steps S6 and S7).

If the designated DB object has expired, the RDBMS 15 returns an error to that effect to the terminal 20 via the interface 16, and the object name of the designated DB object determined to be expired The same object is deleted from the database 11 by deleting it from the management table 13 (step S8).

On the other hand, if the designated DB object is registered without a time limit, or if it is registered with a time limit but is still within the valid period, the RDBMS
15 performs the requested normal database access to the designated DB object (step S11).

Next, it is assumed that the user who has received the login request operates the terminal 20 and inputs a DB object creation command whose expiration date can be specified. RDBMS
When receiving a DB object creation command from the terminal 20, the reference numeral 15 performs well-known DB object creation processing according to the command, and includes the object name of the DB object, the created user name, and the expiration date designated by the command. The object management information is set and registered in the empty entry in the object management table 13 (steps S9 and S10). However, DB with no expiration date specified
In the case of the object creation command, the object name of the DB object and the creation user name are set, but the expiration date is not set.

Next, it is assumed that the login request from the database administrator is accepted, and thereby the database administrator operates the terminal 20 and inputs the user registration command that can specify the expiration date.

Upon receiving the user registration command from the terminal 20, the RDBMS 15 sets and registers the user management information including the user name and the expiration date designated by the command in the empty entry in the user management table 14 (step S9, S10). However, in the case of the user registration command without the expiration date designation, the user name is set, but the expiration date is not set. The above is the case of implementing it in a relational database system,
The present invention is applicable to other database systems as well.

[0030]

As described in detail above, according to the present invention,
For DB objects (database objects) that are known to be unnecessary later,
A database that is set beforehand in the first expiration date setting means when the same object is created, with the unnecessary period as the expiration date, and that registration is canceled later.
For the user, the scheduled cancellation time is set as the expiration date and set in the second expiration date setting means when the user is registered, and various databases are set based on the setting contents of the first and second expiration date setting means. -Since it is configured to manage the expiration date of objects and each database user,
For expired database objects and database users, their registration can be automatically deleted, and effective use of resources can be achieved.

[Brief description of drawings]

FIG. 1 is a block configuration diagram showing an embodiment of a database system to which the present invention is applied.

FIG. 2 is a diagram showing an entry structure of an object management table 13 of FIG.

FIG. 3 is a diagram showing an entry structure of a user management table 14 of FIG.

FIG. 4 is a flowchart for explaining the operation of the embodiment.

[Explanation of symbols]

10 ... Host device, 11 ... Database, 12 ... Data dictionary, 13 ... Object management table,
14 ... User management table, 15 ... Relational database management system (RDBMS), 16 ... Interface (IF), 20 ... Terminal.

Claims (1)

[Claims] 1. A first expiration date setting means for setting an expiration date of various database objects, a second expiration date setting means for setting an expiration date of each database user, and the first aspect. And various database objects and each database based on the setting contents of the second setting means.
A database object and a database user, comprising: management means for managing the expiration date of the user; and automatically deleting the registration of the expired database object and the database user. Expiration date management method.