November 29, 2022 at 3:10 pm
The two wanted screen captures are attached.
select count(*) from sys.dm_db_log_info ( 8 )
result : 932
Med venlig hilsen/Best Regards/Mit Freundlichen Grüßen/ Kveðja/ Distinti saluti/ Met beste groete
Edvard
November 29, 2022 at 3:45 pm
My hunch was right, you are running a database in full recovery mode without log backups! This is not good!
😎
Instead of writing the full instructions here as the documentation and information available are abundant, I suggest you read some of those. Hopefully, your production database does not have the same problem as this can lead to severe data loss. Further, to my previous questions, how do you test your data recovery processes? 😉
November 29, 2022 at 10:01 pm
Also - the default settings for autogrowth are horribly wrong and problematic, especially for the transaction log. That setting of 10% means the next growth is going to be 18890MB - which is ~18GB.
Another thing - the database is set to SQL Server 2008 compatibility where the server is SQL Server 2016 or higher. Unless there are specific issues that have been identified for that database that require staying in 2008 compatibility it should be set to the latest compatibility.
If the source system is actually running 2008 - then it is way past time to upgrade that system.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
Viewing 4 posts - 16 through 18 (of 18 total)
You must be logged in to reply to this topic. Login to reply