ServiceDesk Plus MSP system requirements | Help desk MSP admin guide

System Requirements

Mentioned below are the minimum requirements to run ServiceDesk Plus MSP. You may require more RAM space and high-end processors depending upon the support load, simultaneous access load, and other applications' load installed on the same server.

Inbound Requests Per Day	Hard Disk Type	RAM	Processor	OS
10x - Less than 100	500GB SSD	16GB	1.7GHz to 2.4GHz 10MB to 12MB Cache 4 cores to 8 cores or Any entry-level server grade processor E.g Intel Xeon Scalable - Bronze/Silver Intel Xeon E Family	Windows Server OS (2012-2022) Linux RHEL 8 or above Ubuntu 14.0 or above Cent OS 8 (SE)
100x - Upto 1000	2TB - SSD	16GB/32GB*	2.4GHz to 3.0GHz 12MB to 20MB Cache 6 cores to 8 cores or equivalent technology E.g Intel Xeon E Family
1000x- More than 1000	2TB#/3TB* - SSD	16GB/32GB*	3.0GHz to 4.5GHz 12MB to 30 MB Cache 10 cores to 20 cores or equivalent technology E.g Intel Xeon Scalable Gold/Platinum

* - PostgreSQL bundled is configured as a database

# - More size required if request description/conversations and attachments, etc. are prone to be more, in given business usage.

Supported Browsers

The following is the list of supported browsers. We recommend you update to the latest version of whichever browser you are using for better performance and security.

Mozilla Firefox
Google Chrome
Microsoft Edge

MSSQL

If your ServiceDesk Plus MSP runs on an MSSQL setup, then make sure to host the database server in a separate machine under the same network as the application server. The DB server machine configuration solely depends on no. of databases configured and usage. Please consult with your DBA or Microsoft MSSQL support for system requirements.

Supported MSSQL Versions: 2008, 2012, 2014, 2016, 2017, 2019 and 2022.

PostgreSQL (Applicable to ServiceDesk Plus MSP 10.5 or earlier)

Since PostgreSQL 9.2 requires users to modify kernel resources to allot required resources for Postgres server,

i. Add the the below mentioned entry in /etc/sysctl.conf

kernel.shmmax=536870912

kernel.shmall=131072

ii. Execute sudo sysctl -p /etc/sysctl.conf to reload the configured change.

Note: This is only applicable for Linux OS installations that use bundled Postgres.

How to enable read committed snapshot isolation (RCSI)

All MSSQL databases usually have lock issues, which may affect an application’s optimal performance. To avoid such performance issues in ServiceDesk Plus, enable the read committed snapshot isolation (RCSI) by following these steps:

NOTE: This might take a while to complete and also requires downtime, so please schedule it over a weekend.

Stop ServiceDesk Plus application.
Log in to SQL Management studio.
Take the ServiceDesk Plus database offline by executing
USE master GO ALTER DATABASE <db_name> SET OFFLINE WITH ROLLBACK IMMEDIATE

GO
Enable the read committed snapshot by running
ALTER DATABASE <db_name> SET READ_COMMITTED_SNAPSHOT ON WITH ROLLBACK IMMEDIATE

GO
Bring the database online using
USE master GO ALTER DATABASE <db_name> SET ONLINE

GO
Check if you have enabled RCSI successfully by running the following query

SELECT is_read_committed_snapshot_on FROM sys.databases WHERE [name] = '<db_name>'

If the output to this query is 1, you've successfully enabled RCSI.

You can now start the application. For more information on MSSQL databases and RSCI, go here.

Benefits of enabling the MS SQL Snapshot Mode

Simultaneous user-querying of the database will be possible without any delay or disruption (although load on the application might exceed the usual limits).

User querying records will be maintained in a separate tempdb, which will not be affected by other user queries occurring in parallel or subsequently.

Database tables will be updated only after a transaction reaches completion.