Database Warning : Your database transaction log file size has crossed the threshold

Database Warning : Your database transaction log file size has crossed the threshold

You are getting this email as a result of an enhancement that was made in the 11 version to notify administrators if the SQL Log File Size crossed the threshold. In Service Desk Plus, under Performance Settings in Admin/ESM Directory you have the ability to configure the threshold for the SQL DB's Log File Size. If this threshold is crossed, then the application will trigger out an email to the admins warning them that the threshold log file size has crossed.

 

From the mail, I can see that your transaction log file is 2 GB and hence the application is giving you this warning message. One way to fix this is by increasing the threshold of transaction logs in the application. Consult with your DB admin and change the threshold size as per his recommendation. 

 

Alternatively, this can be addressed by setting the recovery mode in your SQL DB to FULL and also shrinking the Log File size. 

 

You can find the steps to change the recovery mode from SIMPLE to FULL here. As the recovery mode is already FULL, you can follow the steps below to shrink the Log File Size on the DB, and then you should not be getting this warning email. 

 

Note: It is suggested to stop the services of Service Desk Plus service before following the below steps. 

 

1. Login into your SQL Server and Open SQL Server Management Studio. 

In the SQL Server Management Studio, right-click your database, go to Tasks -> Shrink -> Files.




2. In the Shrink File dialog box     

  i)  Under Database files and filegroups choose File type as Log.

  ii) Under Shrink action choose Release unused space




3. Click OK to start shrinking the log file.

Hope this helps. If you still have any queries, please feel free to write to us. 


Best Regards.

    • Related Articles

    • Service Desk services stopped on its own.

      The reason for the crash is becauss the SQL database connectivity was lost. It's looks like this while checking the log file : [15:54:58:066]|[10-11-2018]|[SYSERR]|[INFO]|[72]: 101603933 [ServiceDeskCommon-2] WARN tm.TransactionImpl - XAException: ...

    • Delete Large System error logs records

      Problem: for large Log files (over 1 million records)  When we select the  "delete all" button in the system log viewer in the support tab the system Crashed !  So How can  we delete these large  log files?  Solution: we can delete them from database ...

    • Unable to restore data after changing DBserver to SQL

      After changing the DB server to MSSQL, We tried to restore the data from the backup file, but the restore didn't take place successfully so we followed those steps and everything worked perfectly. Please follow the below steps and re-initiate the ...

    • Performance is slow

      Try access ServiceDesk using the IP address of the Server not using the Alias URL and if the page loads up considerably fast. follow those steps: 1- Go to this path C:\ManageEngine\ServiceDesk\conf and open server.xml file. 2- change the ...

    • Change Postgres Password

      Problem :- Need to change the default password for postgres. Solution :- 1- connect to the database. 2- execute the below steps. servicedesk=# \password Enter new password : Enter it again : 3- Once execute it, do the below. - Open ...