Database user rights

For Snow Inventory Server, a SQL account with sa privileges (or other database-creating rights) is needed during the installation if you create the user before creating the database. It is recommended to reduce the account privileges to a db_owner level after the installation.

For Snow License Manager, a SQL account with sa privileges is needed during installation, and it is recommended to reduce the account privileges to a db_owner level after the installation.

You can use the same account, with sa privileges, for installing both Snow Inventory Server and Snow License Manager. If you create the databases first, you can directly create account(s) with only db_owner privileges.  

The SnowInventoryUser account is used for the database connection by the Snow Inventory Server Application and for administration of the server through Snow Inventory Admin Console. The account must have db_owner privileges on the SnowInventory database.

The account is configured through running the executables in the installation folder (x:\Program Files\Snow Software\Snow Inventory\Server):

The LicenseManagerUser account is used for accessing the Snow databases after the installation and for running the daily Data Update Job in SQL.

The LicenseManagerUser account must have the public Server Role. If the permission View any database is removed from the public Server Role default configuration, the permission must be explicitly granted to the LicenseManagerUser account, in order for the Data Update Job to work correctly.

The LicenseManagerUser account must have db_owner privileges on the SnowLicenseManager database and on the SnowInventory database.

The LicenseManagerUser account must also have the following roles on the msdb database:      

In order to preserve the Data Update Job schedule and notification settings in Snow License Manager 9, the LicenseManagerUser account must be granted select permissions on the tables sysjobschedules, sysschedules, and sysoperators in the msdb database.