If the database is in recovery mode "simple", you can simply truncate the transaction log by issue a "backup log...
with truncate_only" or a "backup log with no_log".
Take a look at the SQL Server books online for more detailed information.
You can read the SQL Server logs and the System Log in SAP to see if you can find out what exactly caused the transaction log to fill up. It could be that there was an open transaction that never got committed. You can also run "dbcc opentran" next time, as soon as you see this problem. But, hopefully you will not get this problem again. The best thing is to set up an alert that triggers a transaction log backup if the log fills up to a determined percentage, like 80%.
Dig Deeper on SAP Basis administration and NetWeaver administration
Related Q&A from Giovanni Davila
Learn how to transfer a client from one server to another in this administration tip from Basis guru Giovanni Davila. Continue Reading
Learn how to return a list of 1,000 transport requests in SAP R/3 PRD in this tip from SearchSAP.com's Basis expert. Continue Reading
Learn fundamentals of transport management and STMS from Basis guru Giovanni Davila in this expert tip. Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.