I just had a transaction log that was growing at about 2 gigs a minute.

It was growing so fast that we felt we had no choice but to stop and restart
the service.

Part of the problem is that we did not know how to track down what the
problem was before taking the drastic measure of stopping and starting sql
server.

What commands or views should one look at in such a situation. Or is there
anything that can be done now to determine what was causing the problem?

I came across the following link:
http://msdn2.microsoft.com/en-us/library/ms176029.aspx

If you have seen this before, please help. It is quite unnerving.

I am running SQL Server 2005, SP1, on Windows 2003.

Tempdb or one of your user databases?

Show quoteHide quote

TempDB was out of control.

Kevin3NF wrote:
Show quoteHide quote

Show quote Hide quote DMV's can show you what transactions are running and how much log space they
are using.

EG

select
  st.session_id,
  t.transaction_id,
  s.login_name,
  s.status session_status,
  s.cpu_time session_cpu,
  s.logical_reads session_logical_reads,
  s.reads session_reads,
  s.writes session_writes,
  t.database_transaction_log_bytes_used,
  sql_details.text session_current_sql_text
from sys.dm_tran_database_transactions  t
join sys.dm_tran_session_transactions st
  on st.transaction_id = t.transaction_id
join sys.dm_exec_sessions s
  on st.session_id = s.session_id
left join sys.dm_exec_requests req
  on s.session_id = req.session_id
outer apply sys.dm_exec_sql_text(req.sql_handle) sql_details
order by t.database_transaction_log_bytes_used desc

David

can someone login as "NT AUTHORITY\SYSTEM "
Need help troubleshooting a memory paging issue
List of running stored procedures
limited permissions on test server for developers
Spid checker query help
Low Disk Space
Delete records in a table with 15 dependencies
how to remove the sql server registry mess?
CHECKING the TRANSACTION LOG
Remote Production Database Issue