Whenever cx faces slowness in PG SQL Setup, below are the first step of actions to check and proceed based on our previous performance tickets. 1. Antivirus are main cause of slowness, high CPU, and memory consumption of PGSQL in many cx tickets. ...
1. To get an idea of how much CPU the queries are currently using, out of overall CPU capacity, run the following statement: DECLARE @init_sum_cpu_time int, @utilizedCpuCount int --get CPU count used by SQL Server SELECT @utilizedCpuCount = COUNT( * ...
Root cause : Chrome has defined Scheduler as a variable and unfortunately the same is used in ServiceDesk Plus in resource management section and Chrome API's 'scheduler' variable is overriding our application's variable (Used in resource management) ...
1. Access your application server and browse to [your drive]:\ManageEngine\<application_name>\bin. 2. Click changeDBServer.bat. Information on the configured database will be displayed. If the database is MSSQL, go to the SQL Management Studio, go to ...
If Applications Manager is up and running and the WebGUI can be accessed, refer to the steps in this knowledge base article for creating support information file. If Applications Manager is down or the WebGUI cannot be accessed, or if the log size ...
Following are the steps to move data from the existing server to a new server, Step 1: Stop ManageEngine ServiceDesk Plus service. Step 2: Kindly Upgrade ServiceDesk Plus if required. Refer to the link below to check if you are in the latest version, ...
Building a test environment is very helpful while upgrading ServiceDesk Plus. When you are planning to upgrade ServiceDesk Plus to the latest version, it is highly advisable to try the upgrade on the test environment first so that you will be ...