My first priority was to fix the problem immediately, so users can access the application and then do root cause analysis. The message I got was the transaction log drive is full and users are unable to access the application, DBAs never want to hear this! The usual DBA question is "what was changed"? In this tip I cover steps that I took to resolve this problem. My SQL Server is clustered and the issue happened after a node failover occurred. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases. The error message I got was: "The transaction log for database 'MyDB' is full. I had a production problem recently, the transaction log grew 1 GB every minute and filled up the entire drive. SQL Server Transaction Log Grows And Fills Up Driveīy: Ranga Narasimhan | Updated: | Comments (11) | Related: More > Database Administration
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |