Update your settings

Large RT.ldf File Size in SQL Server

Hello,

A 30GB transaction log file (.ldf) for your project is significantly large and can cause performance issues. Here's a breakdown of why this happens and steps to reduce its size:

Possible Causes:

• Infrequent Backups: If transaction log backups aren't performed regularly, the log grows continuously.
• Long-Running Transactions: Uncommitted transactions, especially lengthy ones, keep log data active.
• High Transaction Volume: A very active system generates a lot of log data.
• Simple Recovery Model: Using the Simple recovery model truncates the log, but may not be sufficient if there's very high activity.

Recommended Actions:

1. Perform a Full Backup: Crucially, take a full database backup before shrinking the log.
2. Perform Transaction Log Backups: Switch to the Full or Bulk-Logged recovery model and schedule frequent transaction log backups.
3. Shrink the Log File: After backups, you can shrink the .ldf file using SQL Server Management Studio (SSMS) or T-SQL. Be cautious with shrinking as it can impact performance. Right-click the database in SSMS -> Properties -> Files -> Select .ldf -> Shrink.
4. Check for Long-Running Transactions: Identify and resolve any open, long-running transactions.

For detailed instructions and troubleshooting, please refer to these SiePortal resources:

• KB3204: How to shrink the transaction log file (.ldf) in Teamcenter/TC AE?
• KB2802: What considerations should be taken to optimize Teamcenter database performance?

If the issue persists, please open a support request through SiePortal, providing details about your recovery model, backup schedule, and recent system activity.

Sincerely,
Siemens Self Support