Installing the OctoSAM Inventory Database

SQL Server Requirements

We recommend that you use Windows Integrated Authentication for all connections to the database.

The import service service account needs to be in the ‘bulkadmin’ Server Role to bulk insert new data. For best efficiency the service account also needs ALTER permissions on the table SoftwarePackageUsageDetails to be able to truncate the table. If truncate is not possible, the service will fall back to delete operations which take more resources.

Creating the Database

Create a new database using SQL Server provided tools. Choose locations for the database files according to your company standards. Set the database collation to Latin1_General_CI_AS. Compatibility Level SQL Server 2016(130). If you use the OctoSAM License Module, we recommend setting the recovery model to Full

Find the newest create_database_*.sql script in to create the database schema, then run all provided migration scripts up to the desired version.

Migrating from a Previous Version

You need to run the provided migration scripts in exact order to update to the current version. Some migrations may require additional steps and scripts. See the release notes and the comments in the header of each migration script.


Always backup your database before running any migration scripts.

Configure OctoSAM Server Components

All OctoSAM Server components read the global appsettings.json configuration file in a folder pointed to by the OCTOSAM_CONFIGURATION_FOLDER environment variable.

The .net connection string named OctoSAM is used by all server components.

  "ConnectionStrings": {
    "OctoSAM": "data source=localhost;initial catalog=Octopus;integrated security=SSPI"

Rebuilding Indexes and Statistics

The OctoSAM services can optionally re-index the database during housekeeping.


This feature requires additional database permissions. Use only when your organization does not already have policies for scheduled rebuilding of indexes and statistics in place. Consult with your DBA before activating this feature.

SQL Server Express Edition

We do not recommend the use of SQL Server Express Edition for productive installations. Its limits on size are usually too constraining.