This page lists the server, client, and SQL Server requirements for installing MRM BI.
Server Software/Hardware
LNOS Reporting Servers
Intel® Xeon® Processor E3 or better
Microsoft Corporation's Windows Server® 2008R2 (64-bit) or 2012 R2 (preferred)
1.5 - 2 gigabytes (GB) RAM per vCPU, minimum 4 GB
Disk Space 50 GB for data and logs
Note: Must be in the same or trusted domain as the database servers.
Database Server (DB, SQL)
Intel® Xeon® Processor E5 or better
16 GB RAM (minimum)
At least 30 GB of available disk space on system partition.
Dedicated (separate) storage for Data, LOG and TempDB preferred.
Size and Input/output operations per second (IOPS) requirements will vary per customer volume and throughput requirements.
RAM requirements will also change, based on volumes, since Microsoft Corporation's SQL Server operates better with more RAM.
Windows® 2012 R2 or later operating system or higher
SQL Server SQL 2012-2016, either standard or enterprise edition
Note: Must be in the same or trusted domain as the reporting servers, usually deployed on the same server as Descartes Route Planner™ (if non-hosted).
SQL/RP Compatibility Matrix
MRM BI Version |
SQL Server 2012 |
SQL Server 2014 |
SQL Server 2016 |
17.05 |
X |
X |
X |
18.01 |
X |
X |
X |
18.05 |
X |
X |
X |
Note: It might be possible to run Descartes MRM BI on a higher version of SQL provided SQL compatibility level is configured to match the supported versions, however this is not guaranteed.
Client Hardware/Software
The current minimum requirements are as follows:
Intel® Core™ i5 Processor or similar
Microsoft Windows® 7 Professional (64-bit) or higher
4 GB DDR3-1600 RAM
Internet Explorer® 9.0 or later (11 preferred)
Microsoft Edge® browser (Descartes Reporting Services™ 17.05 and later)
Google Chrome™ browser (Descartes Reporting Services 17.05 and later)
Browser Configuration
Descartes Reporting Services requires a few browser configuration changes to work correctly. It is recommended that these changes be pushed out through group policy to avoid users being required to individually configure their computers. Descartes Route Planner will function without these changes, but the users may experience irregularities or may not be notified of certain errors.
The three major configuration changes are:
Setup site as a trusted site
Setup site in compatibility mode
Setup refresh on "Every visit to this webpage"
In addition, it is recommended to disable "Show Friendly HTTP Error Messages" so that more detailed messages are available to customer support. For step-by-step instructions on how to configure these settings please see the Configure Internet Explorer® for Use with Descartes Reporting Services™ section in the User and Configuration Guide.
SQL Installation Requirements
Memory Configuration
SQL Server memory should be configured to use most of the memory available on the SQL Server; however, there should be a memory buffer to allow for normal day-to-day user/operating systems.
Disk Configuration
Application Data files (MDF, NDF) should exist on a disk subsystem (LUN/Physical) separate from the operating system.
Application Log files (LDF) should exist on a disk subsystem (LUN/Physical) separate from the operating system. Log files should be separated from the data files as well.
TempDB Data Files (NDF) should exist on a disk subsystem (LUN/Physical) separate from the operating system, Data & Log Files.
Example of a properly configured 16-core SQL Server:
Drive Letter |
Disk Usage |
Example SQL File |
C |
Windows OS & SQL Server Install |
*None* |
G |
MRM BI Primary Data files |
MRM_BI.mdf |
H |
MRM BI Staging Data Files |
MRM_BI_RPStaging.mdf |
I |
MRM BI Log Files |
MRM_BI.ldf |
J |
TempDB Data Files (x4) |
Tempdb1..4.ndf |
K |
TempDB Data Files (x4) |
Tempdb5..8.ndf |