Mercury Pre-Installation Checklist

Mercury is a Windows 64-bit .NET application that uses SQL Server (2012+) to house its internal database.

There are two types of installation: server (which creates Mercury’s internal database); and client (which installs the Mercury application on the PC).  A server installation also installs the client, so some items appear in both lists.

A note on database access: user permissions to ERP databases are the purview of your IT department.  Mercury does not make any changes to production databases, but we do ask that users be granted permissions to read production data.   The simplest way is to create a windows group and add the group to db_datareader.  Your admins can choose a more granular permissions route.  Mercury does not have a specific requirement.

 

PC and Installation Package

  • PC from which Mercury is being installed: Windows 7+ 64-bit
  • Installation package: InstallMercury.msi (downloadable from here)

 

Server Installation (typically 1 – 5 minutes plus client-installation time)

  • SQL server name (and instance, if any) that will house the Mercury database.
  • A name for the Mercury database that will be created (we suggest “Mercury”)
  • SQL admin credentials: windows auth, or SQL login.  SQL admin privileges are required in order to create Mercury’s database.  Windows authorization is preferable.
  • .NET Framework 4.7.2 – see Client Installation below
  • Windows privileges to install software on PC (because server-install also installs the client)
  • Company / organization name (as it should appear in output; also used for licensing)
  • Company / organization logo (as it should appear in output; any graphics file will work)

Server Post-Installation Tasks – Database Permissions and Mercury Users

  • Ensure your users have read and write permissions to the Mercury database. Details depend on
    your own SQL security setup – Windows account, Windows security group, or SQL login.
  • From within Mercury (Tools > Admin Tools > Users), add users as needed, and (if reports already
    exist) grant access as needed. For details, see the Mercury reference documentation.

Client Installation (typically 1 – 5 minutes plus .NET, if required)

Try Mercury for Free

Try Mercury on a fully-functional 14-day trial. Download and install to use with your own data or try Mercury in a remote desktop session using our demo data. 

Try Mercury For Free

  • Download & Install

    Download and install a fully-functional 14-day trial; use it with your own data. (We can help you install and configure).

    System Requirements




  • Over the Internet

    Try PivotViews in a remote desktop session using our demo data; no installation required.

    System Requirements

    None! (Well, you do need a PC that can run Microsoft’s remote-desktop protocol, which includes practically any Windows PC.)