A production database contains the data you are using for production tasks such as creating and updating features. Depending on the data model you are using, data in a production database can be used to create a digital or hard-copy map or chart or a specific type of data. The data in a production database usually corresponds with a data model and product class in the product library.
For instance, if you load the Vector Map Level 2 (VMap 2) data model into your product library so you can create Topographic Line Maps, a VMap 2 database should be used as the production database.
Data models and product classes
Both data models and product classes refer to the data or map product you are producing using the product library. The difference is that the data model includes all the datasets and tables within the schema, while a product class can include a subset of the datasets and tables in the data model.
With the product class, feature classes and tables can be included selectively, which allows you to create different versions of the same data model for specific purposes. For instance, you may want to create a version of the VMap 1 product class that does not have any void areas. You could either modify an existing version of the product class or create a new one with the void area feature classes omitted.
For a production database, you need to indicate which data models are compatible as well as the product classes and what the current one is for the database. Though the data might be compatible with several data models, only one can be selected as the current one for use with a production database.