In the database setup you define the structure of database tables (the database table definitions) by their properties, in an .inf file. These database tables, along with many secondary tables, will typically be created in a SQL Server database. All data from all records that you enter or import into all the data sources in your Collections application will be stored in that database. One or more data sources may refer to a particular .inf file which is associated with its own table in the database.

For example, the Internal object catalogue and External object catalogue are two data sources which are both associated with collect.inf and collect.inf has its own table in the SQL Server database, along with many secondary tables for indexes and saved searches etc.

 

Datasets

A database table can be divided into virtual sub sets, known as datasets. These are not separate tables, only a subdivision of the one database table by record number range. This allows the user to search those datasets separately, or to search a combination of datasets. You can also screen off parts of a database table from certain users by this division. Generally, datasets are used to group together records that logically belong together. For example, you could divide a catalogue database up into a books dataset, an articles dataset, a serials dataset, and an audio-visual materials dataset.
In the database setup you define a dataset by its properties.

See also

Accessing the database setup

How to create a new database or dataset