Ali_SQLDBA (1/9/2010)
Thank you for your immediate response.Yeah, at that point of time there was no other go for us. So I shrinked the t-log. i was able to recover 3gb. when th nightly jobs rbuild and update stats have started, we lost the recovered 3 gb and the errorlog is filled up with "The transaction log for database is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases". So this error message is gonna be resolved by adding free space? Is that correct.
My T-log size is 43058.81 MB
Thanks
Ali
S,u r correct adding more space ll help u.
First check where ur t-log files located
select filename from sys.sysaltfiles
where db_name(dbid)='Dbname'
My T-log size is 43058.81 MB
43 GB is very huge.
How often did u run the log backups?
Can u tell me the total Db-size.
Muthukkumaran Kaliyamoorthy
https://www.sqlserverblogforum.com/