Bound Databases and Enforced Integrity

---

When creating a database, you are offered the options of Integrity Enforced and Bound (DDFs created).

• Integrity Enforced means it enforces any triggers and referential integrity defined within the database. Generally, the only time you would not want this option checked is when doing a large download of data from an existing database.
• A Bound database associates a database name with a single set of Data Dictionary Files (DDFs), which refer to only one set of data files. If DDFs are bound, you can't use those DDFs for several databases, nor can you refer to the data files by more than one set of DDFs. This protects the database from tampering. If you delete a bound database, the associated DDFs are also deleted.

Binding a database ensures that the MicroKernel enforces the database's defined security, referential integrity (RI), and triggers, regardless of the method you use to access the data.

Even if you do not bind your database, Pervasive.SQL automatically stamps a data file as bound if has a trigger, has a foreign key, or has a primary key that is referenced by a foreign key. Thus, a data file may be part of an unbound database, but be bound. In such cases, the MicroKernel enforces integrity constraints on the file as if it were part of a bound database.

When you create a bound database or bind an existing database, Pervasive.SQL stamps every dictionary and data file with the name of the bound database. Also, Pervasive.SQL stamps every data file with the name of the table associated with that data file. In addition, when you add new tables or dictionary files to the bound database, Pervasive.SQL automatically binds them.

---

Caution
Under certain conditions related to relational database structures, access to data through the Btrieve interface is restricted. If you plan to use both SQL/ODBC and Btrieve to access your data, and your database is bound or uses triggers, stored procedures, security, or referential integrity, please refer to Interactions Between Btrieve and Relational Constraints in Advanced Operations Guide.

---