Why is it a good idea for the DBMS to update the catalog automatically when a change is made in the database structure? Could users cause problems by updating the catalog themselves? Explain

Explanation:

A catalog is a directory where information about the location of file or database is stored

(a) It is good for DBMS to upgrade the catalog automatically when there is a change in the database structure.

It has the following benefits;

- The updated form of the database can be made available and accessible to other users

- The data of the database will remain in a stable and consistent state

- There will not be a need to execute the update query to update the database.

-If there is no update automatically, only users that made changes will be able to have access to the database

(b) Yes, users can cause problems by up dating the catalog manually.

The following will be the disadvantage when the catalog is updated by users;

- Updated database will not be seen until the user update manually by themselves

- Persistence and consistency of problems

The catalog is defined as a directory in which the information about the database is stored. This catalog contains information about the location of any file or database. That DBMS update its catalog automatically when any change in the database is made is a good choice, since any user could enter and consult either a file or a database that is kept updated. If DBMS does not automatically update the database, only users who make any modifications to that database will be able to access that updated information, this would be a typical inconvenience if users update the catalog manually.

Explanation:

saas delivery model;