September 27, 2011 at 8:32 am
Hi every body one of my cluster server raises the alert like below
Log File Size is CRITICAL ** then what is the solution for this ?
means can shrink the file or take T-log backup ?
Regards,
Satya.
September 27, 2011 at 8:35 am
http://www.sqlservercentral.com/articles/Transaction+Log/72488/
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
September 27, 2011 at 9:24 am
You must immediately back up your transaction log file. Maybe, decrease the time interval of T log backups if possible.
While the backup of your transaction log files is created, SQL Server automatically truncates the inactive part of the transaction log.
Also,
Set the size of the transaction log files to a large value to avoid the automatic expansion of the transaction log files.
If you read Gail article, you should get clear about T logs.
Regards,
Sushant
Regards
Sushant Kumar
MCTS,MCP
September 27, 2011 at 9:26 am
SKYBVI (9/27/2011)
You must immediately back up your transaction log file. Maybe, decrease the time interval of T log backups if possible.
Not necessarily. That'll only help if the cause of the large log is the lack of log backups (as opposed to the several other possible reasons). The first step should be to figure out why the log is full or growing, then take appropriate action.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply