•
|
Controls access to the data. The DBMS can act as a watchdog to prevent the wrong people from using the data.
|
•
|
Structures the data so it can be interpreted by other applications. The DBMS ensures that all the data adheres to the database structure, so that other computer programs can work with the data using common methods.
|
•
|
Keeps the data safe and prevents it from getting garbled or lost. The DBMS facilitates backing up the data in case of catastrophic loss, and also accesses it in a consistent manner to prevent the data from suffering inadvertent damage.
|
•
|
Makes it easy to add new information, find it, update it, and delete it. The DBMS readily accepts new data and provides tools that you can use to locate, update, and remove information as you see fit. It verifies that the data inserted fits within defined attributes for the database fields.
|
•
|
Allows you to analyze relationships among different sets of data. The DBMS stores the data in a way that allows you to examine how any piece of data relates to any other piece of data.
|
Manipulates settings for Pervasive client and server components. See Configuration Reference in Advanced Operations Guide.
|
||
Converts one version of MicroKernel files into another version. See Converting Data Files in Advanced Operations Guide.
|
||
Sets up Data Source Names (DSNs) for client and engine interfaces. See DSNs and ODBC Administrator in SQL Engine Reference.
|
||
Used to configure and maintain gateway locator files for the Workgroup engine. See Setting Up a Gateway Configuration in Getting Started With Pervasive PSQL.
|
||