September 13, 2002 at 3:47 am
Hi,
One pretty large database overnight decided to grow it`s transactionlog too big for the drive. The problem is, is that it won`t let me truncate the file now. I`ve tried backing up the transaction log, to no avail. I`ve even tried using shrink, but that still hasn`t done any good. Is there any reason why a log file won`t truncate?
Andy.
September 13, 2002 at 4:32 am
A thought..
select * from sysprocesses and then for all spid's run dbcc inputbuffer for all spid's to find out what all is going on ur server/database
by killing some spid's may help...
Best if you could stop and start the server.....
Prakash
Prakash Heda
Lead DBA Team - www.sqlfeatures.com
Video sessions on Performance Tuning and SQL 2012 HA
September 13, 2002 at 9:59 am
I have stopped and started the server since.
THe log has been truncated, but I can`t shrink the damn thing!
Andy.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply