# Installing Agents in Remote Offices - Endpoint Central MSP - How To

## How to customize the size of Endpoint Central MSP Transaction Log in MS SQL Server?

## Description

This document explains you the steps involved in reducing the size of the Endpoint Central MSP logs in MSSQL server. If the size of the transaction logs of Endpoint Central MSP increases then it might cause server startup issues. So, it is recommended to clean up these logs periodically or customize the size of the Endpoint Central MSP transaction logs.

This document is applicable only for customers using Endpoint Central MSP with MSSQL database.

**Note:** You can also refer to the steps recommended by Microsoft:

1. [http://msdn.microsoft.com/en-us/library/bb522469.aspx](http://msdn.microsoft.com/en-us/library/bb522469.aspx)
2. [http://msdn.microsoft.com/en-us/library/ms190488.aspx](http://msdn.microsoft.com/en-us/library/ms190488.aspx)

## Steps

The following steps need to be performed on the computer where Endpoint Central MSP Server is installed:

1. Go to **Run**, type **services.msc**
2. Search for **ManageEngine DesktopCentral MSP Server** and stop the service.

The following steps need to be performed on the computer where the MS SQL database is configured:

1. Go to SQL Management Studio.
2. Navigate to the **desktopcentral** database and right-click it.
3. Choose **Properties** and click **Options**.
4. Select **Recovery Mode** as **Simple**.
5. Under **New Query**, connect to the Endpoint Central MSP database and execute one of the following queries. You can choose to either shrink the size of the log or alter the size of the log as mentioned below:

   1. **Shrink the size of the Endpoint Central MSP database**

      The following query is recommended by Microsoft to shrink the size of the Endpoint Central MSP database. Using this query, you can determine the size of the database and shrink the available free space in terms of percentage.

      If you specify the value as "20%", then the size of the database will be shrunk by 20% if there is available free space. This will not work for smaller databases. It is recommended only for large databases.

      ```sql
      DBCC SHRINKDATABASE (database_name, target_percent)
      ```

      **Example:**

      ```sql
      DBCC SHRINKDATABASE (desktopcentral, 20)
      ```

   2. **Alter Database Modify File**

      This can be used to alter the size of the transaction logs. You can use this to increase or decrease the memory used for storing the transaction logs.

      Refer to the Microsoft article for more details:  
      [Steps to Alter Database File and Filegroup Options](http://msdn.microsoft.com/en-IN/library/bb522469.aspx)

      ```sql
      ALTER DATABASE <DATABASENAME>
      MODIFY FILE (NAME = "<DATABASENAME>_log", MAXSIZE = 5GB)
      ```

      **Example:**

      ```sql
      ALTER DATABASE desktopcentral
      MODIFY FILE (NAME = "desktopcentral_log", MAXSIZE = 5GB)
      ```

      In this example, the Endpoint Central MSP log size will not exceed 5 GB.

6. Restart DesktopCentral MSP Server from the machine where it is installed.

You can see that the Endpoint Central MSP log size will now be reduced in the MSSQL database.