Method and system for managing external routines in a database management system

Abstract

A method for managing an external routine in a computer implemented database management system includes creating a first table for storing external routines in a data store coupled to the database management system. An external routine is stored in the first table so that the database management system is allowed to automatically manage any modification related to the external routine and to control access to the external routine such that administrative support is minimized.

Description

FIELD OF THE INVENTION [0001] The present invention relates to database management systems and in particular, to managing routines, such as stored procedures or user defined functions, in a database management system. BACKGROUND OF THE INVENTION [0002] Database management systems (DBMS) maintain and manage data stored in databases. Management includes storing, deleting, retrieving and updating the data. Typically, data stored in a database includes plain values, e.g., numbers and alphanumeric strings, and complex objects such as images, documents and spatial data. The DBMS typically is hosted by a database server that is accessible by a plurality of client systems via a network. [0003] In state of the art systems, the DBMS is capable of invoking executable code to manipulate the data in the database. In some systems, when instructed, the DBMS can automatically load and execute the code. Such executable code, known as an external routine, can be a stored procedure (STP) or a user def...

AI Technical Summary

Benefits of technology

[0009] According to versions of the present invention, external routines are stored in the data store and treated as database content that is managed directly by the database management system. Synchronization processes already in place for ensuring consistency throughout the database can be utilized to ensure consistency between the external routines and catalog entries. In addition, the access control policies applying to data in the database can be easily extended to the external routines thereby protecting them from unintentional modifications and malicious users.

Problems solved by technology

While this configuration is convenient, it presents a number of logistical challenges.

For instance, because the routines reside in the file system, inconsistencies between the file system and the catalog can arise, e.g., after a backup or restore function.

This is an added burden on the system administrator, and becomes particularly tedious if the database is partitioned over a plurality of nodes.

Moreover, because the routines reside in the file system, security concerns can arise.

The access control policies for the server are not necessarily identical to those of the DBMS, and therefore, a client who has access to the file system can inadvertently or intentionally modify, delete or replace a routine.

This can cause serious system disruptions that require administrative attention.

To prevent this, the system administrator has the added burden of controlling access to the file system and also protecting the external routines.

Images