https://community.fabric.microsoft.com/t5/Report-Server/The-transaction-log-for-database-Database-is-full-due-to-LOG/m-p/4688000#M40644 <P><img /></P><P>&nbsp;</P> Mon, 12 May 2025 00:10:49 GMT FarrukhData 2025-05-12T00:10:49Z https://community.fabric.microsoft.com/t5/Report-Server/The-transaction-log-for-database-Database-is-full-due-to-LOG/m-p/4688000#M40644 <P><img /></P><P>&nbsp;</P> Mon, 12 May 2025 00:10:49 GMT https://community.fabric.microsoft.com/t5/Report-Server/The-transaction-log-for-database-Database-is-full-due-to-LOG/m-p/4688000#M40644 FarrukhData 2025-05-12T00:10:49Z https://community.fabric.microsoft.com/t5/Report-Server/The-transaction-log-for-database-Database-is-full-due-to-LOG/m-p/4688002#M40645 <P><SPAN>If you are truncating the transaction logs, this means you are breaking the T-Log LSN (Log Sequence Numbers). This follows that if disaster comes, you would not be able to restore your T-Logs and there would be no option for you to do point in time recovery. If you are fine with this situation and there is nothing to worry, I suggest that you change your recovery model to Simple Recovery Model. This way, you will not have extra ordinary growth of your log file.</SPAN></P> Mon, 12 May 2025 00:11:38 GMT https://community.fabric.microsoft.com/t5/Report-Server/The-transaction-log-for-database-Database-is-full-due-to-LOG/m-p/4688002#M40645 FarrukhData 2025-05-12T00:11:38Z