How to prepare for the SLM9 upgrade

Blog Post created by geoffrey.macquet Employee on Mar 21, 2019

The intention of this blog is to prepare you for a smooth Snow License Manager 9 Upgrade, with some useful hints to raise the awareness and the knowledge about the process.

Please note that we strongly recommend to run the upgrade guided by either professional services or a qualified Snow partner. Please contact your account manager or your local Snow partner for further information and assistance. If you are unsure who your account manager is, please submit a ticket to support.

Please be advised that any resulting issues during the upgrade from uncertified resources is not covered by the Support Agreement and therefore needs to be remedied by Snow Professional Services or certified Snow Partners.


  1. Prerequisites

    1. License Key

      To get your Snow License Manager 9 Key, please contact your account manager or your local Snow partner. In some cases you may contact the Backoffice directly.

      Please be aware that the company (organization) name should not exceed 35 characters as described in KB0017826.

    2. System Requirements

      Verify that the servers meet the system requirements for this product. System requirements and
      information on dependencies on other Snow products are gathered in the document System
      Requirements for all Snow products, which is available for download on this Knowledge Base Article.
    3. Software preparations

      Use Microsoft SQL Server 2012 Standard or later (recommended version 11.0.7469.6 - SP4).

      Use Microsoft Windows Server 2012 or later.

      Install ASP.NET 4.5 with all features enabled as a role on your server.

      Install .NET Framework 4.7.2 or later on your Snow License Manager application server.

      Have Snow Inventory version 6.0.3 which is the minimum database version supported by SLM 9.0.0.

      If you are using the IIS (Internet Information Services) to host other web applications, make
      sure you have a web hostname or a specific port assigned to the Snow License Manager

      SQL Server Database compatibility level: The minimum version is 100 (corresponding to SQL Server 2012). This setting is configured per database in SQL Server and must be manually checked if the database has been migrated from SQL Server 2008.
  2. Readiness Upgrade Checks

    1. Checking minimum DB Size and Growing Policy

      By default, our setup packages create the databases not specifying a minimum size or a growing policy. The growing policy impacts performance because Microsoft keeps 1MB as default. Please, add the following content to check these settings:


      SLM Data File: Growing 4096MB, (Recommended maximum: Unlimited)
      SLM Log File: Initial size 4096, Growing 1024MB, (Recommended maximum: Unlimited)

      Please, respect the values for Log file. SQL Server creates something called “virtual disks” in that file. The formula applied by mixing 4096MB + 1024MB keeps those virtual files in a reasonable number (300-600 hundreds) for large DBs what improves performance. The partner will need to shrink log files using the SQL Server Management Studio tool to reduce any existing Log file to 4096 if the current size is higher.

      The growing policy is one of the most common problems while talking about performance in our customer base.
    2. Administrative accounts for in-scope Snow application server and SQL server

      Please verify that the used accounts do have enough permissions; Ensure the SQL user account with database  does have administration privileges (sa or equivalent account with sysadmin rights).

      Verify that the LicenseManagerUser SQL account belongs to the db_ower role in SnowLicenseManager and SnowInventory databases. This account is used to perform the upgrade process.

      This role could be lost due to security restrictions, after a migration from SQL Server 2008 or while recovering a database in a Test Environment.

      LicenseManagerUser should also have SQLAgentOperatorRole, SQLAgentReaderRole and SQLAgentUserRole.

      This is default applied settings when upgrading to SLM8.


      SQL version, If SQL 2016 by default, Microsoft does not apply optimized code unless and Administrator allows that. Please, check that:

      Database (SnowInventory and SnowLicenseManager) > Properties > Options > Query Optimized Fixes = 0N
    3. Additional Information for Inventory Sources in the SMACC settings
      All Inventory databases configured in SMACC with "Enable data update job" to active must be on Inventory 6.0.3.
      The data update job in SLM 9 requires that no configured Sites in any Inventory Source in any CID for the same Inventory database overlap. Example of an overlap:

      Inventory Source 1, site: Company%
      Inventory Source 2, site: CompanyUK

      Snow Management and Configuration Center checks for Site overlap when adding a new Inventory Source but existing overlaps must be fixed before upgrading to SLM 9.0.0.

    4. Backup

      Verify in scope backup/restore procedures for SQL DB's and application server(s) request full backups to be completed in line with the planned upgrade.

      Microsoft SQL Server
      Full backup of SnowInventory and SnowLicenseManager database

      Also request full application settings backups of the following locations on the SLM8 server:

      Snow License Manager Compliance Settings
      ..\Snow Software\Snow License Manager\Services\Licensing\SnowSoftware.LicenseManager.Licensing.Service.exe


      Event Store


      Import Settings
      ..\Snow Software\Snow License Manager\Services\ImportTool\DataImport\Import\*.*

    5. Calculating space requirements

      Snow Inventory Server
      The database will grow a 20% and must have enough space in the transaction log before starting the upgrade. Use the following formula to estimate its size (temporarily, it can be reverted to the original size after upgrade):

      (Total SnowInventory DB size) * 0.5 +
      (SnowInventory.inv.DataMetering size + SnowInventory.inv.DataMeteringConcurrency size) * 2.85

      Snow License Manager
      Total size of the SLM database will grow up to 30-40% after upgrade and first initial DUJ run.

    6. Checking custom procedures and reports

      Several database changes may or will impact custom procedures and reports. All existing customizations must be analyzed to check compatibility by professional services.

      How to identify existing custom procedures:
      USE SnowLicenseManager
      select * from tblSystemCustomProcedures

      How to identify existing custom reports:
      USE SnowLicenseManager
      select * from tblReport where IsCustomReport = 1
    7. Checking the current logs to identify any existing errors

      In order to facilitate troubleshooting if an error appears after the upgrade, all existing logs should be checked looking for any existing issue before upgrading the products


      Snow Inventory Server Checks:



      Snow License Manager Server Checks:

      %PROGAMFILES%\Snow Software\Logs


      %PROGAMFILES%\Snow Software\Snow License Manager\Web\Logs


      %PROGAMFILES%\ Snow Software\Snow LicenseManager\Services\ImportTool\DataImport\ErrorRows


      Snow License Manager Database Server:
      USE SnowLicenseManager
      select * from tblErrorLog order by LogDate desc

  3. New features which have been implemented with SLM 9

    – Tracking of licensing model changes

    – Manual exclude computers during the Compliance calculation

    – Hypervisor Technology and high availability of datacenter and cluster

    – Reports for cost estimation of Microsoft Windows Server

    – Inkremental Data Update Job (DUJ 2.0) – Performance optimization

    – Direct access to the UserGuides

    – Discovery of Google Cloud Computer Engine

    – Different Oracle optimisations (needs the latest version of the Snow Inventory Oracle Scanner)
    Processing of Oracle Datenbase Data
    License determination of Oracle Databases
    Detailed lifetime support information about Oracle Datenbases
    Oracle WebLogic Server investigation and inventory
    Tracking of Oracle Database inventory

    When you have upgraded to Snow License Manager 9, be aware that the first run of Data Update
    Job will take a considerable amount of time to run; subsequent runs of Data Update Job will take
    considerably less time.

    We recommend to always use the latest version of Snow License Manager in order to stay updated
    with the latest features and corrections. Please read the Release Notes for details.

  4. FAQ

Are Snow Inventory Clients (3.x) compatible with Snow License Manager 9?

Yes, however it is highly recommended to update them to the latest version of the Snow Inventory Agents 6 as there have been lots of improvements.

Note that the macOS 6.x Agents requires Inventory Server 6.0.0 or higher.

If you want to check which Agents are compatible with which OS checkout this blog:

Using earlier Snow Inventory agents to scan older operating systems


Can I upgrade to Snow Inventory 6 and continue running Snow License Manager 8?

Yes, INV 6 and SLM 8 are compatible. However, this compatibility is by design, as Inventory 6 is a prerequisite for SLM 9. We do not recommend this configuration to persist longer than it takes the customer to carry out the SLM 8/9 upgrade. 

Can I run Snow License Manager 9 with Snow Inventory 5?

No, SLM 9 and INV 5 are not compatible.

Can I upgrade from Inventory 3 to Inventory 6 directly?

Yes. We recommend doing this for users who plan to update to SLM 9.

Why are we rolling out INV6 & SLM9 in two phases?

The 6/9 update involves changes to the Snow Inventory and Snow License Manager databases, with new tables, and new structures for data processing.


This blog may be continuously updated.