Read transaction log file

• durai nagarajan

  SSCoach

  Points: 15778

  More actions

  April 25, 2013 at 1:16 am

  #1609798

  Basically log is some works in circular motion, once the log file is full it will try to over write the backed up log or before full backup db point logs.

  It grows only when it is needed and above overwrite not possible and It never returns the space to OS automatically.

  go through gails article given below

  http://www.sqlservercentral.com/articles/Administration/64582/

  Regards
  Durai Nagarajan

• Gail Shaw

  SSC Guru

  Points: 1004504

  More actions

  April 25, 2013 at 2:21 am

  #1609815

  vinu512 (4/25/2013)

  ---

  One small doubt that is still bugging me is that when i see the size of the log, of the newly restored db, it still shows 17 GB.....if it does not have any transactions before the time it was restored then what does the 17 GB log have??

  Probably 17GB of empty space. A restore recreates the DB as it was at time of backup, down to the exact file sizes. Hence if you back up a database with a 17 GB log file and restore it elsewhere, the log file will be 17GB in size.

  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

  We walk in the dark places no others will enter
  We stand on the bridge and no one may pass

• vinu512

  SSCoach

  Points: 15729

  More actions

  April 25, 2013 at 10:35 pm

  #1610195

  Thaank you very much Durai and Gail. The last week was a very important lesson. Learnt it the hard way, but learnt it well.

  Vinu Vijayan

  For better and faster solutions please check..."How to post data/code on a forum to get the best help" - Jeff Moden[/url] 😉