How to solve the MS SQL log size issue?
I have noticed that
ServiceManagement_log file size on SCSM DB server is above 150 GB. How to
solve it? is it normal?
Step 1: The Recovery Model for the database can
be set to ‘Simple’ in SQL Server Management Studio.
- Use SQL Server Management Studio to connect to SQL server.
- After connecting to the appropriate instance of the SQL Server Database Engine , in Object Explorer, click the server name to expand the server tree.
- Expand Databases, and, depending on the database, either select a user database selecet (ServiceManagemenet) database.
- Backup of transaction logs is needed in case of any failure.
- Right-click the database, and then click Properties, which opens the Database Properties dialog box.
- In the Select a page pane, click Options.
- The current recovery model is displayed in the Recovery model list box.
- Optionally, to change the recovery model select a different model list. Change the option to Simple either from Full or Bulk-logged.
- Click OK.
Step 2: Shrink the database files
- Use SQL Server Management Studio to connect to SQL server.
- After connecting to the appropriate instance of the SQL Server Database Engine , in Object Explorer, click the server name to expand the server tree.
- Expand Databases, and, depending on the database, either select a user database selecet (ServiceManagemenet) database.
- Right-click the database, and then click Tasks, select Shrink then Files.
- On the Shrink File window, change the File Type to Log. You can also choose to either Release unused space, Reorganize pages before releasing unused space, or Empty file by migrating the data to other files in the same filegroup, in our case first the first option Release unused space.
- Click OK to start shrinking, it will reduce the size and reclaim more space on the server disk.
Comments
Post a Comment