Solution : https://service.sap.com/sap/support/notes/421644 (SAP Service marketplace login required)
Summary :
The SAP Note addresses the issue of a full SQL Server transaction log, which prevents further transactions due to lack of space. The primary reasons for the log overflow include insufficient log size, infrequent log backups causing untruncated logs, and extended transactions hindering truncation. Solutions proposed include manual log file enlargement, increasing frequency of log backups, and adding additional log files to accommodate larger transaction volumes. Recovery models discussed are the Bulk-Logged and Simple models, which differ in their handling of transaction logs and data recovery. For immediate log space release, manual truncation with backup is advised, followed by a full database backup.
Key words :
sql server regularly sets approximately, bulk-logged recovery model reason, bulk-logged recovery modelthis option, simple recovery modelthis option, implicit simple recovery model, dbcc printed error messages, line 1the log file, display long-running transactions, 'bulk-logged' mode, 643amdbcc execution completed
Related Notes :
| 1420452 | FAQ: Restore and recovery with MS SQL Server |
| 555223 | FAQ: Microsoft SQL Server |
| 534036 | SAP LT: System settings for conversions |
| 400251 | Index creation fills up transaction log |
| 363018 | File management for SQL Server |