Skip to main content

How to solve the ServiceManagement_log size issue on SCSM DB server?


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.
  1. Use SQL Server Management Studio to connect to SQL server.
  2. After connecting to the appropriate instance of the SQL Server Database Engine , in Object Explorer, click the server name  to expand the server tree.
  3.  Expand Databases, and, depending on the database, either select a user database selecet (ServiceManagemenet) database.
  4. Backup of transaction logs is needed in case of any failure.
  5. Right-click the database, and then click Properties, which opens the Database Properties dialog box.
  6. In the Select a page pane, click Options.
  7. The current recovery model is displayed in the Recovery model list box.
  8. Optionally, to change the recovery model select a different model list. Change the option to Simple either from Full or Bulk-logged.
  9. Click OK.

Step 2: Shrink the database files
  1. Use SQL Server Management Studio to connect to SQL server.
  2.  After connecting to the appropriate instance of the SQL Server Database Engine , in Object Explorer, click the server name to expand the server tree.
  3. Expand Databases, and, depending on the database, either select a user database selecet (ServiceManagemenet) database.
  4. Right-click the database, and then click Tasks, select Shrink then Files.                                      Shrink the log in SQL Server Management Studio
  5. 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.                                                                                                                    On the Shrink File window, change the File Type to Log.
  6. Click OK to start shrinking, it will reduce the size and reclaim more space on the server disk.



Comments

Popular posts from this blog

Exchange OWA Error (Something Went Wrong)

Exchange OWA Error (Something Went Wrong) Exchange 2016 Cu8 on Windows Server 2012 R2 gave error on OWA, ECP will work if administrator doesn’t have a mailbox. else even ecp will throw the same error. An unexpected error occurred and your request couldn't be handled. X-ClientId: 15BED63F62FB4FDB809703ED2534C19D request-id 1ac56275-a1ab-48cf-9f82-880c49767a19 X-OWA-Error Microsoft.Exchange.Diagnostics.ExAssertException X-OWA-Version 15.1.1415.4 X-DAGServer COMM X-DAGerver COMM Date:11/07/2018 3:30:06 PM Description: Unable to find the certificate with thumbprint [Thumb code] in the current computer or the certificate is missing private key. The certificate is needed to sign the outgoing token. or invalid or expired ' Microsoft Exchange Server Auth Certificate' Solution: Create new  Microsoft Exchange Server Auth Certificate  1.      Open Exchange admin Center ECP, then go to servers, certificates, find Microsof...

CredSSP Encryption Oracle Remediation RDP issue

  CredSSP Encryption Oracle Remediation RDP issue An update released by Microsoft ( KB 4093492 )on  May 8, 2018 , for Windows 10 Operation System was targeted to change the default settings CredSSP from  Vulnerable  to  Mitigated . However, post patching this caused an issue where the patched clients were blocked from communicating with unpatched servers over RDP protocols. This has been reported to cause an error thrown by Windows RDP as below: Solution: Use the group policy settings changes described below to rollback the changes to ‘Vulnerable’ state to allow RDP access. 1. Open Group Policy Editor, by executing  gpedit.msc 2. Policy path:  Computer Configuration -> Administrative Templates -> System -> Credentials Delegation Run  gpedit.msc  and expand  Administrative Templates Expand  System Expand  Credential Delegation Edit  Encryption Oracle Remediation Select  Enabled  and change Production Leve...

How to configure E-Mail notification in WSUS

How to configure E-Mail notification in WSUS The WSUS server can be configured to send e-mail notifications of new updates and reports on the status of the WSUS network. Notifications will be sent whenever the WSUS server synchronizes new updates, and status reports can be sent daily or weekly.  Set up e-mail notifications In the WSUS Administration console, click  Options in the left pane. In the center pane, click  E-Mail Notifications . Click the  General If you want update notifications, select the  Send e-mail notification when new updates are synchronized check box. In the  Recipients box, type the e-mail addresses of the people who should receive update notifications. Separate the names with semi-colons. If you want status reports, select the  Send status reports check box. In the  Frequency box, select either  Daily  or  Weekly . In the  Send repo...