November 3, 2010 at 1:31 am
Hi All, During weekend due to some reason the log file has grown to 100+ GB whereas usually it consumes 40+ GB. I want to find what was going on with that DB at that time. Could you please help me on this?
Thanks,
sqlstart
November 3, 2010 at 1:46 am
sqlstart wannabe (11/3/2010)
Hi All, During weekend due to some reason the log file has grown to 100+ GB whereas usually it consumes 40+ GB. I want to find what was going on with that DB at that time. Could you please help me on this?
Daily we are seeing this type of post...u can find the solution here itself.
http://www.sqlservercentral.com/search/?q=log+file+growing
http://www.sqlservercentral.com/Forums/Topic1010214-146-1.aspx
http://www.sqlservercentral.com/Forums/Topic1013706-146-1.aspx
there is number of things to be log grow..You can't find the reason please post back.
Muthukkumaran Kaliyamoorthy
https://www.sqlserverblogforum.com/
November 3, 2010 at 3:52 am
Check : select name,log_reuse_wait_desc from sys.databases
Check on which your database is waiting?
Vamsy
November 3, 2010 at 4:50 am
sqlstart wannabe (11/3/2010)
Hi All, During weekend due to some reason the log file has grown to 100+ GB whereas usually it consumes 40+ GB. I want to find what was going on with that DB at that time. Could you please help me on this?
Could be because of maintenance tasks like index rebuild/reorganize OR any heavy DML operation like inserting/deleting millions of rows
-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done;-)
November 3, 2010 at 5:01 am
I don't know of a way after the fact unless you had a trace running ....
I run transaction log backups every 15 min, so I look at when the backup files got big and try to match up against jobs that were running. I now have a server side trace automatically running so I can help troubleshoot these kinds of things.
November 4, 2010 at 8:17 am
homebrew01 (11/3/2010)
I don't know of a way after the fact unless you had a trace running ....I run transaction log backups every 15 min, so I look at when the backup files got big and try to match up against jobs that were running. I now have a server side trace automatically running so I can help troubleshoot these kinds of things.
There is a way - get ApexSQL's log tool and you can see every DML that happened in the database.
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply