March 23, 2011 at 9:40 am
hi ,
one of our database log got full. we have trancate log and we have shrink log file as like below.
backup log database db_name with truncate_only
use db_name
dbcc shrinkfile(db_name_log)
it's ran successfully.but log usage showing like as same before . please assistence on this.
March 23, 2011 at 9:44 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
March 23, 2011 at 10:11 am
Read Gail's article. It has some good advice in it.
Also, you should not be regularly truncating and shrinking. If you are in full mode, set up transaction log backups.
March 23, 2011 at 11:41 am
Steve Jones - SSC Editor (3/23/2011)
Also, you should not be regularly truncating and shrinking. If you are in full mode, set up transaction log backups.
And on that point... Managing Transaction Logs[/url]
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
March 24, 2011 at 6:21 am
hi,
the database in bulkloged mode.please assistence on this
March 24, 2011 at 6:54 am
See the above-mentioned articles. Bulk-logged, like full recovery, requires regular log backups.
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
March 24, 2011 at 8:28 am
i've had this on simple logged recovery models as well. in our case reinitializing replication usually solves it
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply