Share
ReportHello,
I am dealing with a probably strange situation in a production AX 2012 R3 environment SQL datafiles, which I am trying to understand and would need some help.
The database data (mdf) is about 300 GB and transaction log (ldf) file 700+ GB with low utilization (% used), so last weekend I thought I should shrank the log. So, I was waiting until Friday end for all users to logoff, then I took a transaction log backup and shrank the log file to 256 GB, using the SQL Management Studio GUI.
Everything looks great after that, however today Monday I see both data (mdf) and transaction log (ldf) files size & date unchanged, as of last Friday end-date (for the data file) and Saturday when shrank the log (for the log file)!
Which comes to a surprise with many users working on the system today/Monday.
How can this be explained? Does it seems normal to you?
Related settings and observations:
- Database recovery model if FULL, and full database backup (once a day), differential backups (every 2 hours) and transaction log backups (every 30 minutes) were all taken without problems today.
- Transaction log utilization (% used) was fluctuating normally during the day and occasionally dropping close to zero due to often log backups. Still, transaction log date stays the same as of last Saturday when shrank.
All responses (
Answers (
291,280
