• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1241
  • Last Modified:

SQL 2005 - Set Transaction Logs Size

Hi all

On our corporate SQl server we hve numberous Database on or two if which grow very aast and large,  we have tried setting the trnsaction log file sizes by

SQl Server Management Studio > Right Click Database > Properties > Files > Initial Size " 14000, Grow by 10%,  Restricted file growth 2,097,152,, but the transaction log files regularly grows to 4 -6 GB in size and we hve to manually truncate the log file to release teh space

Any thoughts on why this woudl be happening.

What is the best way to set q a limit on teh ransaction log of a database,

Regards, Alan

0
Singnetsvc
Asked:
Singnetsvc
  • 2
  • 2
1 Solution
 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
if the database is in full recovery mode, it requires regular (hourly, for example) transaction log backups
using those backups, it will make the log file will reuse it's internal space, and not grow endless.

if you are 200% sure you will never need a recovery to a point in time, you could change the database to simple recovery, hence the space can be reused automatically.
0
 
dportasCommented:
The person who is responsible for backing up these servers needs to understand Recovery Models and determine what kind of backup and recovery strategy to use. If your are regularly growing and shrinking then that person probably isn't doing their job properly, which ought to be a cause for concern. You could start here:
http://technet.microsoft.com/en-us/library/ms189275.aspx
0
 
SingnetsvcAuthor Commented:
The Database is a transaction log for TFS Version control.

A full backup of teh database backup sets are carried out every four hours.

Is there a reason why teh max file size specified is esceeding it set limit, i was under the impression that if the max value was reached it woudl recycle teh oldest informatino first etc etc

Alan.
0
 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
>Is there a reason why teh max file size specified is esceeding it set limit, i was under the impression that if the max value was reached it woudl recycle teh oldest informatino first etc etc

the max file size for the transaction log will keep the file from growing, but also from transactions to be committed when the t-log is full.

so, if you have a tlog backup (note: a full backup will NOT clear the t-log !) every 4 hours, and the t-log file is still growing, you have 2 possible situations:
* the transactions in those 4 hours require more space than the size allocated
   => reduce the time interval of the backups from 4 hours to 2 hours, for example, during high traffic
   => ensure all transactions do only update the rows/columns they really need to update

* there is some old open transaction keeping the log from recycling.
  => DBCC OPENTRAN should tell

0
 
SingnetsvcAuthor Commented:
Link lead to script that help automate process
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now