|
sql
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
transaction log growing very quicklyAbout 4 days ago (ish) our db's transaction log was about 3 GB and growing
fairly slowly. Right now it's 23 GB and growing extremely quickly. There hasn't been an increase in the amount of DB traffic on our server and I'm sure something is wrong. How can I find out what is causing it to grow? Chris You can use SQL Profiler to capture the application that is hitting your
database. You can also try this KB http://support.microsoft.com/kb/283784 Show quote "Chris" <f***@email.com> wrote in message news:69642002-46E4-4F8F-869A-63EE1D80C024@microsoft.com... > About 4 days ago (ish) our db's transaction log was about 3 GB and growing > fairly slowly. Right now it's 23 GB and growing extremely quickly. There > hasn't been an increase in the amount of DB traffic on our server and I'm > sure something is wrong. How can I find out what is causing it to grow? > > Chris Chris
What is RECOVERY mode of the database? Is it FULL? If it is you have to start backup LOG file , I would also suggest you read and understand about RECOVERY models and its impacts on the database in the BOL . Show quote "Chris" <f***@email.com> wrote in message news:69642002-46E4-4F8F-869A-63EE1D80C024@microsoft.com... > About 4 days ago (ish) our db's transaction log was about 3 GB and growing > fairly slowly. Right now it's 23 GB and growing extremely quickly. There > hasn't been an increase in the amount of DB traffic on our server and I'm > sure something is wrong. How can I find out what is causing it to grow? > > Chris I've noted that logs grow exponentially when someone kicks off a large
data-intensive query and then cancels. If you don't need the FULL option, switch to the SIMPLE option for the database which will truncate the logs when a full backup runs. Using the profiler as mentioned by bass_player also is a good start. -- Show quoteRegards, Jamie "Chris" wrote: > About 4 days ago (ish) our db's transaction log was about 3 GB and growing > fairly slowly. Right now it's 23 GB and growing extremely quickly. There > hasn't been an increase in the amount of DB traffic on our server and I'm > sure something is wrong. How can I find out what is causing it to grow? > > Chris > run sp_who2 active. look for spids with extremely large I/O and/or CPU
then run dbcc inputbuffer(spid) to see what code is executing. only spids > 50 are to be evaluated. low spids are system processes. -- Show quoteKevin G. Boles TheSQLGuru Indicium Resources, Inc. "Chris" <f***@email.com> wrote in message news:69642002-46E4-4F8F-869A-63EE1D80C024@microsoft.com... > About 4 days ago (ish) our db's transaction log was about 3 GB and growing > fairly slowly. Right now it's 23 GB and growing extremely quickly. There > hasn't been an increase in the amount of DB traffic on our server and I'm > sure something is wrong. How can I find out what is causing it to grow? > > Chris  |
|||||||||||||||||||||||
Other interesting topics