on 05-18-2016 5:26 PM
Hi Arman,
The problem is simple and you have to resize the log.
You have to maintain the maximum limit for the transaction log.
- Logon to the MSSQL server
- Select the Database SOL and right click
- Select the option files and decrease the size of the maximum growth.
Before performing the activity , first of all shrink the transaction log.
Then schedule a transaction log backup in DB13 hourly basis.
With Regards
Ashutosh Chaturvedi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ashutosh
Thank you for your help.
I'm trying to shrink the data but I don't have any available free space.
What can you suggest for this point?
Regards,
Arman
Hi Arman,
Looks like your DB is set to full Recovery Model. To fix the current issue, restart the SAP Application & DB (so that all active transaction are killed) and then take a t-log backup, you will get some free space in t-log.
To prevent it in future:
1. If the recovery model is Full schedule a t-log backup and set the frequency of 1hr. You can later change the frequency depending on how the system is being used and the logs are generated.
2. If you don't need point in time recovery (since it's not Business Critical system) you can change the recovery model to Simple. The t-logs will still be generated but will be cleared as soon as the transaction is committed.
Thanks,
Manas
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.