Ksubscribers transaction log large

PROBLEM

The ksubscribers transaction log file is large.

SOLUTION

Note: We strongly suggest that a SQL database backup be taken against the database prior to running any SQL command.

You can easily shrink the transaction log file by following the steps below.

Execute the SQL Query below to change the database into SIMPLE recovery mode. This will allow maximum shrinkage of the transaction log:

Alter database <YourDatabaseName> Recovery simple
GO

Execute the SQL Query below which will attempt to shrink the transaction log to 10 MB. This should remove all the empty space from the transaction log:

DBCC SHRINKFILE('ksubscribers_log',10)

ADDITIONAL INFORMATION

You can run these commands at any time as this will not affect the SQL performance of the Kaseya server.

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Contact us