The transaction log (Servicedesk_log.ldf) for database 'servicedesk' is full

The transaction log (Servicedesk_log.ldf) for database 'servicedesk' is full

There are two methods to fix this issue.
Method 1

To fix this issue, we have to detach ServiceDesk database, after detaching we can delete the transaction log ( .LDF log) 
and attach the ServiceDesk database back.

The important part in this process of attaching database will be removing the log path.The attaching database configuration window will show the path of the log (.LDF log), we have to remove the log path only then we will be able to attach the database

Following steps are given below, explains in detail about the process of attaching and detaching the database.


# Stop the ServiceDesk Plus service.

# Connect to the SQL database, take a SQL backup and detach service desk database.


# After detaching the database, goto the location where the .LDF log file is located.

Follow the screenshots given below to delete the .LDF log

Eg:-

C:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA
 
Delete the "mike_log.LDF" log file

# Import and add the detached Servicedesk database as per the screenshot is given below.




# In order to complete ServiceDesk database attaching process, remove the .LDF log file path .

The important part in this process of attaching database will be removing the log path.The attaching database configuration window will show the path of the log (.LDF log), we have to remove the log path only then we will be able to attach the database. 



# Restart the ServiceDesk Plus service. 

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Method 2

Shrinking the transaction logs is an alternate method to resolve the issue.We could use the below query to bring down the size of those logs.

==========================
USE Database_Name
GO
DBCC SHRINKFILE (File_Name, Target_Size)
GO
==========================

Database_Name -->> the database on which we are going to execute the query.
File_Name -->> The file which needs to be shrinked.
Target_Size -->> To what size the file needs to be shrinked.(size is mentioned in MB)

Find below few screenshots which can help you understand things in detail:

Screenshot 1: The database JamesWilcox with log file name JamesWilcox_log with initial log size 1744 MB is going to be shrinked to size 1MB .





          • Related Articles

          • Steps for taking Full Backup

            The following instructions is to perform a manual backup in ServiceDesk Plus – MSP, Step 1: Stop ManageEngine ServiceDesk Plus – MSP service. Step 2: From the command prompt, go to [ServiceDesk Plus-MSP-Home]\bin directory and ...
          • Database Schema of MSP

            The database schema is accessible from within the ServiceDesk Plus MSP application. Navigate to Reports -> New Query report -> Here you can click on the two icons available to view the Schema like shown below, For more details on the important table ...
          • Move database from one machine to another

            Following is the procedure to migrate your ServiceDesk Plus – MSP database from one MSSQL to another. Step 1: Stop ManageEngine ServiceDesk Plus – MSP service. Step 2: Take a backup of the existing data and configuration under MSSQL database. From ...
          • Error While connecting default Postgres Database

            If you are getting the below error while connecting the postgresDB , please follow the steps below : Error : psql: FATAL: no pg_hba.conf entry for host “::1”, user “postgres”, database “servicedesk”,SSL off     Please open pg_hba.conf under ...
          • How do I convert the database from PGSQL to MSSQL?

            Step 1: Stop ManageEngine ServiceDeskPlus – MSP service. Step 2: Take a backup of the existing data and configuration under PGSQL database. Open CMD as an admin and execute  command to start the data backup. ...