The DSM MDB Log size is increases every day . Due to this, there is space constraint issue in MDB server.
If a DB is Backed up regularly with "Remove inactive entries from transaction log" option a shrink is done.
Also we can refer to the following MS articles to shrink a transaction log:
They contain details on how to shrink databases and log files. (dbcc Shrink database and dbcc shrink file)
Further relevant considerations:
Here two resources that we can use:
- How to stop the transaction log of a SQL Server database from growing unexpectedly http://support.microsoft.com/kb/873235/
- THIS LINK IS THE MOST USEFUL AND COVERS MANY SCENARIOS: http://msdn2.microsoft.com/en-us/library/ms175495.aspx
That last link discusses the following items:
Troubleshooting a Full Transaction Log
Backing up the Log
Freeing Disk Space
Moving the Log File to a Different Disk
Adding a Log File on a Different Disk