Codenica logo
     IT Audit and Inventory Software
User Guide
main user guide menu »
Chapter: Database
( Codenica Inventory )

Configuring the Database

By default, Codenica Inventory uses a database designed to operate on an internal file system. Despite its processing speed, the mechanism is unable to match the high level of reliability of Microsoft SQL Server. Therefore, one of the first actions a Codenica Inventory user take should be to transfer data to an MSSQL server.

The application is compatible with any Microsoft SQL server (version 2005 or later), so that both free versions of MSSQL Express and commercial MSSQL systems can be used. With the migration mechanism, the application transfers data very quickly between databases on a single SQL server and between different servers. The MSSQL compatibility mechanism requires the user to define the access path to a selected instance (local or in a network) of a SQL server and indicate the target database. (The application automatically creates new databases with user-defined names.)
See the description of database settings »

Codenica Inventory is PC inventory management software that allows the user to create and maintain an unlimited database (any limitations are imposed by MSSQL itself). The inventory system can use any number of databases and any number of MSSQL servers. This makes it possible to independently maintain multiple inventories. The data consolidation mechanism is particularly useful, allowing users to maintain a joint inventory (data from individual company branch inventories consolidated into a single separate inventory).
See the description of loading and consolidating data »

Network Use

As an IT inventory management system, Codenica Inventory can share data with any number of users.
(A license is required for each workstation.)

Configuring the Application for Network Use

1.)The application must be installed on any workstation requiring access to it (every computer where a user may need to view, add, or edit inventoried data).

2.) The next step is to configure the application on the first computer according to individual preferences, using the options available in the Settings »
Database settings can be configured in:
Settings > Database »
• Create a database on a network MSSQL server (free or commercial).
• Select the following application operation mode: Network (shared database).

Once the configuration procedure is complete and the selected database has been connected, the application will prompt to migrate data. The user should migrate data only when configuring the first access workstation. The other workstations will only be connected to the database.
Note: If the data migration option is selected for an empty database, the application will understand it as a command to remove the data from the connected database.

3.) Finally, copy the settings file from the first (configured) workstation to the other workstations to avoid having to repeat the configuration tasks on each one. To do this, copy the
"[application folder]\App\Config\AppConfig.xml" file from the first computer to the same location on the remaining workstations.


WARNING: The application is not a terminal software version. Therefore, it is not recommended to share a single instance of the application by any system of remote desktop services (RDS). Sharing data in this manner adversely affects the data consistency and integrity of the entire inventory. (Write protection in network mode works ONLY when the application is launched from different workstations, requiring different host names.) This also violates the terms of the license agreement. The application should be installed separately on each access workstation and activated with individual licenses.

User Privileges

Codenica Inventory allows the user to define user logins and passwords. The privileges system is very detailed and supports allowing limited access to specific application functionalities for selected users. Every action made by an application user is recorded in the history for a given object (including the date and computer name) and in the application's event log.

To set user privileges, use the following command:
Menu > File > Settings > User Privileges

See Settings > User Privileges »

Creating Backup Copies

To create a backup copy of data, use the following command:
Menu > File > Database > Save Data to File (backup)

The bottom panel of the application provides information about the most recent backup and the time elapsed since it was created. It is recommended to create data backups as often as feasibly possible and to secure them as much as possible.

It is also recommended to periodically create a backup copy of the entire application folder to ensure that program settings, lists and print configurations, templates, etc. are also saved, apart from the database.

Loading and Consolidating Data

To load data from a backup file, use the following command:
Menu > File > Database > Open Data from File

The data loading process first deletes existing data and then inserts data from the file into the database.

To consolidate data from a file with an existing database, use the following command:
Menu > File > Database > Add Data from File (consolidation)

The data consolidation process adds the data stored in a file to an existing database. Data already in the database will not be deleted.


Example of Consolidating Data

A company consists of multiple branches, each maintaining its own, internal inventory. A designated person from the head office establishes a separate joint inventory. The inventory is periodically updated (consolidated) with data files e-mailed from company branches in order to maintain an updated, joint inventory that includes data for the company and all of its branches.