Main > Knowledge Base > Developer resources > Administration > Data structure in 1C:Enterprise 8 > Developer resources > Administration > Data structure in 1C:Enterprise 8 > Developer resources > Administration > Data structure in 1C:Enterprise 8

Data structure in 1C:Enterprise 8

This article describes the database files and tables supported by 1C:Enterprise 8, as well as the data types stored in these files and tables. The article covers both the file and client/server Infobase modes.

This information should be used solely to analyze the location and composition of data used in 1C:Enterprise and is intended for the developers of applied solutions and 1C:Enterprise 8 Infobase administrators. This information must not be used for processing this data using any methods that are not supported by the inherent features of 1C:Enterprise 8.

Infobases, configuration repositories, auxiliary data, and temporary data

This article only describes the data that 1C:Enterprise uses on a constant basis regardless of the actions performed by specific configurations or actions related to the user's choice of certain files. It does not describe configuration files, data dumps, external data processors, or other files that are external in relation to 1C:Enterprise 8.

The data that 1C:Enterprise uses on a constant basis may be divided into 5 groups according to their purpose and importance:

Different methods are used for storing data belonging to different groups. The ability to manage both file and client/server Infobases adds variety to the ways data is stored.

Infobase structure

The data that defines the logic of 1C:Enterprise-based applications is stored in the Infobase. The Infobase is stored in a database as a set of tables. 1C:Enterprise 8 can use one of the five DBMS for this:

Both Infobase modes (file and client/server) have similar formats (which do differ in small ways) at the level of database objects (tables, fields, indexes, and so on). Some information about this format is provided below.

The entire Infobase is presented in a database as a set of tables. There are several tables among them that must be included in the presentation of each Infobase.

During startup, 1C:Enterprise checks whether the abovementioned tables are available in the Infobase, and should any of them be missing, the following warning is displayed: "Infobase corrupted". If all the abovementioned tables are missing, that means that the Infobase is empty. If this is the case, the tables are created.

A list and the structure of other database tables is defined by a specific configuration, i.e., by the metadata objects defined in this configuration. The name of each table consists of a letter prefix followed by a number. The prefix defines the purpose of the table, while the number helps distinguish between tables of a similar purpose that relate to different metadata objects. If IBM DB2 is used as a DBMS, table aliases instead of table names have this structure.

If a configuration defines at least one exchange plan with the "Distributed Infobase" checkbox selected, the following tables are created:

Below are the various metadata objects that can correspond to various tables.

If IBM DB2 is used, table alias prefixes start with letters instead of underscore character.

The number of these tables depends on the configuration functionality and may be rather large. Naturally, 1C:Enterprise does not check the availability, integrity, or consistency of their data. It is therefore important that any database where 1C:Enterprise 8 Infobase is stored is protected from unauthorized access and is only modified with 1C:Enterprise tools. Use the Administration — Verify and Repair function integrated into Designer to check the database.

It is also important that any backup or restore operations with a database that stores an Infobase are performed with the entire database only. Therefore, we recommend that you use database backup tools integrated into the DBMS. You can copy the file 1cv8.1cd to back up an Infobase in the file mode.

You can use the Administration — Dump Infobase command in Designer to upload all data that relates to an Infobase (and only this data) into the specified file (dump file). You can use the reverse command Restore Infobase to download all the data from a dump file and replace the existing data in the current Infobase with it. You can use these commands for backing up Infobase data both in file and client/server modes.

Configuration repository

The configuration repository is used in the group development of configurations for storing the history of configuration versions, including the last (current) version. The entire repository is stored in a single file, 1Cv8ddb.1cd, which is located in a directory specified as a configuration storage directory.

The data stored in this file is vitally important for developing configurations using group development tools. This data should, therefore, be backed up.

Event Log

The Event Log relates to an Infobase and stores information on events that occur during user interaction with this Infobase. This information is not mandatory for the operation of 1C:Enterprise-based applied solutions, but it may be important from an organizational point of view.

Event Logs are stored in 1Cv8Log directories, one for each Infobase. Each directory contains the 1Cv8.lgf file and several files named yyyyMMddhhmmss.lgp, where yyyy is the year, MM the month, dd the number of the day in the month, hh the hour, mm the minute, and ss the second. For example, "20070525200000.lgp". The 1Cv8.lgf file contains the general event log data. Each of the yyyyMMddhhmmss.lgp files contain a fragment of the Event Log for the corresponding period. A file name matches the moment the period begins. The length of the period is defined by the Divide the Event Log saves by periods setting of the Event Log.

In the file mode of an Infobase, the Event Log is stored in an Infobase directory (the same one that stores the file of the Infobase itself). For instance, if an Infobase is stored in file C:\EnterpriseInfoBase\1cv8.1cd, the Event Log will be stored in the C:\EnterpriseInfoBase\1Cv8log directory.

In the client/server mode of an Infobase, the Event Log is stored in a subdirectory of a cluster working directory. The subdirectory name is defined by an Infobase identifier. For instance, C:\Program Files\1cv82\server\reg_1541\fb9d9cc4-ccd0-4be7-87e8-c5182945291e/1Cv8Log.

Profiles

Profiles contain data that does not impact the operation logic of a 1C:Enterprise 8-based system. This data is not necessary, but storing it can enhance user experience with the system. Profiles can be used to store the format and positions of windows and dialog boxes, font, color, filter settings, and so on. Loss of this information cannot negatively impact the system operation.

Profiles differ according to the types of information they store. The types of profiles used by 1C:Enterprise 8 are provided in a table below:

Data type

Examples of data stored

Location

Client computer

- Whether the immediate window is open.
- Text editor settings.

<User application data>\1C\1cv82\1Cv8.pfl. Example:
C:\Documents and Settings\User\Application Data\1C\1cv82\1Cv8.pfl

Client computer

- Client settings files, backup cluster data and other service data

Example:C:\Documents and Settings\All Users\Application Data\1C\1Cv82\1cv8conn.pfl

Infobase

- Authentication mode at 1C:Enterprise startup from the Debugger.
- The directory that contains the last configuration repository save file.

The Files table of the database that stores the Infobase.

Infobase and user

- Dynamic list settings.
- Event Log filter settings.

The Files table of the database that stores the Infobase.

Computer and infobase

- Comparison settings of configuration files.
- Settings for the global search in all of the configuration texts.

<User application data>\1C\1cv82\<Infobase ID>\1Cv8.pfl. Example:
C:\Documents and Settings\User\Application Data\1C\1cv82\4129dbdb-b495-41cb-99ea-ef315060a03e\1Cv8.pfl

Computer, infobase and user

- Position of the Syntax Assistant pane.
- A list of variables for quick lookup in Debugger.

<User application data>\1C\1cv82\<Infobase ID>\<User ID>\1Cv8.pfl. Example:
C:\Documents and Settings\User\Application Data\1C\1cv82\4129dbdb-b495-41cb-99ea-ef315060a03e\E8D87DA4-A087-4145-95E7-D613E0F7CB64/1Cv8.pfl

1C:Enterprise 8 in Designer mode

- Designer pane positions.
- Colors of the module editor in Designer.

<User application data>\1C\1cv82\1Cv8cmn.pfl. Example:
C:\Documents and Settings\User\Application Data\1C\1cv82\1Cv8cmn.pfl

1C:Enterprise 8 in Enterprise mode

- Calculator dialog properties.
- Table document properties.

<User application data>\1C\1cv82\<Infobase ID>\<User ID>\1Cv8cmn.pfl. Example:
C:\Documents and Settings\User\Application Data\1C\1cv82\4129dbdb-b495-41cb-99ea-ef315060a03e\E8D87DA4-A087-4145-95E7-D613E0F7CB64/1Cv8cmn.pfl

1C:Enterprise 8 Startup dialog

- Size and location of the startup dialog box.
- Settings of infobase parameter setting dialog boxes.

<User application data>\1C\1cv82\1Cv8strt.pfl. Example:
C:\Documents and Settings\User\Application Data\1C\1cv82\1Cv8strt.pfl

Profile data is read when 1C:Enterprise 8 is started and is written when 1C:Enterprise 8 is closed normally. This is why some user settings might be lost in the event of abnormal termination.

Other auxiliary data

In addition to profiles, the application data directory may contain other files with data that can enhance the 1C:Enterprise 8 user experience. Among them are the following:

We recommend that you place the nhsrv.ini file in the directory where the HASP License Manager executable file is stored. You can use Activity Log/Server Activity Log to check whether the HASP License Manager found and read the configuration file.

Temporary data

Temporary data is only needed during one or more simultaneous 1C:Enterprise sessions.

Several simultaneous sessions jointly use data that is related to the entire file Infobase and is necessary for Infobase data locking, as well as for some other tasks. This sort of data is stored in the same directory as the Infobase file.

1C:Enterprise 8 running in Designer mode creates temporary files of a similar purpose for the configuration repository and stores them in the configuration repository directory.

The data that is only used during a single 1C:Enterprise session is stored in temporary files created in the directory defined by Microsoft Windows as the temporary files directory. In this case, the client application uses the temporary files directory of the current Windows user, for example, C:\Documents and Settings\User\Local Settings\Temp. Either the system temporary files directory or the application data directory of the user on whose behalf the working processes of 1C:Enterprise server are started is used for the 1C:Enterprise server (for example, C:\WINNT\Temp).

Next page: Publishing 1C:Enterprise infobase via HTTPS protocol in IIS





© 1C LLC. All rights reserved
1C Company respects the privacy of our customers and visitors
to our Web-site.