SQLite:

This option is ideal for use on a single user. Choosing SQLite means the database is self-contained, serverless, and zero-configuration, meaning it does not require any additional setup.

MySQL:

Suitable for team environments, selecting MySQL allows for multiple users to access and manage shared data concurrently.
This can include syncing settings for folders, catalogs, file descriptions, previews, and other shared resources among all team members. However, to use MySQL, additional configuration is necessary.
Here you can read a short tutorial how to setup MySQl database: Using Project Manager for Team: guide for installing and configuring database

Path to SQLite database file.

 

Using this type of database is not require for any special knowledge.

Simple install and use.

It is not recommended to use SQLite database to sync a database for multiple users.

Use the MySQL database for this.

Reset path:

Button to reset the SQLite database path to default.

Options to setup a MySQL database, with fields for hostname, port, username, and password to connect to the MySQL server.

Here you can read a short tutorial how to setup MySQl database: Using Project Manager for Team: guide for installing and configuring database

The new caching system allows storing assets in the database, significantly speeding up file search operations. This applies both for searches in the Explorer tab and for finding missing assets in the Asset Tracking tab. Also, this works for search even using “Batch Relink” tool, which comes bundled with Project Manager.

 

Allow Cache:

A toggle to enable or disable the caching of assets for faster access on searching.

Cache Directories:

Specify directories to caching. By default, only directories used in Project Manager on the treeview are cached.

Update Cache:

This will restart caching all of your asset files.

Import Database:

Option to import a database from one type to other.

Avalaible options: Import from SQLite to MySQL.  Import from MySQL to SQLite. Import from Connecter.

Convert Paths:

Utility to convert file paths within the database, for instance after moving assets to a new location.

Restore Database:

Feature to restore the database from a backup.

Optimize Database:

Function to optimize the database for performance. Project Manager now provides additional options to optimize the database, including “Optimize,” “Remove Missing Directories,” and “Remove Missing Directories & Files.” These options allow users to maintain the health and efficiency of the database.

Apply:

Button to save and apply changes made to the database settings.

This option allows you to convert all the file paths in the database to local paths. It’s particularly useful when you’re working on a standalone machine and need all the asset paths to be local. For example, network paths like “\\NetworkDrive\Assets\image.jpg” would be converted to a local path like “C:\Assets\image.jpg”.

This option enables you to convert all the file paths in the database to network paths. It’s beneficial when you’re working in a team environment and need all the asset paths accessible from any machine on the network. You can specify mapped paths to ensure that the network paths are correctly mapped to the local drives on each machine. For instance, a local path like “C:\Assets\image.jpg” would be converted to a network path like “\\NetworkDrive\Assets\image.jpg”.

This option allows you to convert file paths in the database using a specific mask or pattern.

It’s useful when you need to perform a more complex conversion that can’t be achieved with the standard local or network conversion options. You can use regular expressions (regex) to define the mask, providing a powerful tool for manipulating file paths. Use this option if you moved your assets to a new location, for a new drive, or rename a directory outside the Project Manager, for example.

For example, you could use a regex to convert paths like “C:\OldFolder\Assets\” to “D:\NewFolder\Assets\”.

Enable:

Checkbox to turn on the automatic backup feature.

Path to backup:

Specifies the location where backups are stored.

Backup every:

Sets the frequency of backups in hours.

Store the last:

Determines how many backups to retain.