December 8, 2017 at 7:06 am
coolchaitu - Friday, December 8, 2017 6:42 AMBrandie Tarvin - Friday, December 8, 2017 6:32 AMcoolchaitu - Friday, December 8, 2017 6:24 AMBrandie Tarvin - Friday, December 8, 2017 5:37 AMAside the R drive, how is your log file set up? With a maximum size? Or with Auto Grow?And how much of that 100 is being taken up by the log file for this one database verses the regular database files and other database log files?
What about the system DBs? Are they on the same drive? If so, have you looked at tempdb to see how big it is compared to the others?
It is setup to auto grow. System dbs are on different drive. How to find out what consumed the log drive
You haven't answered the rest of my questions.
The log file is taking full 100gb
Okay. So the log file for this database is the only thing on the drive.
Here's some last resort troubleshooting options (really last resort if this is production). Stop everything on the DB. Set the DB single user. Backup the database (FULL) and the transaction log. Run checkpoint against the database (if it allows you to get into it). Truncate the log file (don't shrink it unless truncate doesn't work. Please note that checkpoint doesn't always happen immediately. You may have to wait a while.)
Turn database back on to multi-user and run a server side trace to monitor transactions against the database. This will help you identify the offending transaction.
December 8, 2017 at 7:25 am
Brandie Tarvin - Friday, December 8, 2017 7:06 AMcoolchaitu - Friday, December 8, 2017 6:42 AMBrandie Tarvin - Friday, December 8, 2017 6:32 AMcoolchaitu - Friday, December 8, 2017 6:24 AMBrandie Tarvin - Friday, December 8, 2017 5:37 AMAside the R drive, how is your log file set up? With a maximum size? Or with Auto Grow?And how much of that 100 is being taken up by the log file for this one database verses the regular database files and other database log files?
What about the system DBs? Are they on the same drive? If so, have you looked at tempdb to see how big it is compared to the others?
It is setup to auto grow. System dbs are on different drive. How to find out what consumed the log drive
You haven't answered the rest of my questions.
The log file is taking full 100gb
Okay. So the log file for this database is the only thing on the drive.
Here's some last resort troubleshooting options (really last resort if this is production). Stop everything on the DB. Set the DB single user. Backup the database (FULL) and the transaction log. Run checkpoint against the database (if it allows you to get into it). Truncate the log file (don't shrink it unless truncate doesn't work. Please note that checkpoint doesn't always happen immediately. You may have to wait a while.)
Turn database back on to multi-user and run a server side trace to monitor transactions against the database. This will help you identify the offending transaction.
Thanks Brandie
May 2, 2018 at 6:23 pm
So, did you ever find the offending transaction?
--Jeff Moden
Change is inevitable... Change for the better is not.
May 2, 2018 at 9:40 pm
Jeff Moden - Wednesday, May 2, 2018 6:23 PMSo, did you ever find the offending transaction?
Yes Jeff
Viewing 4 posts - 16 through 18 (of 18 total)
You must be logged in to reply to this topic. Login to reply