Question : How to control growing size of an MSSQL database transaction log file

Recovery mode of a MSSQL 2000 SP3 database is set to full.
Size of database is about 80GB.
Backup of the transaction log takes place every 2 hours daily.
Transaction log file is set to grow by 500MB at a time, with no restriction on size.

The transaction log file seems to be growing out of control. Presently at about 45GB! and growing (or possibly stabilising at this size). I once shrank it, using the shrink-file option in the data maintenance wizard, to 1GB. But within a fortnight, it re-generated to its present size.

I had always thought that by regular backups of the transaction log, it will keep the physical file small.Without the need to manually shrink it. And if I do, how would I know what size would be appropriate? I have tried arbitrarily setting a maximum size to allow it to grow to (1GB). But within hours the application crash, complaining of inadequate log space.

Would really appreciate some expert advice, for which my thanks in advance.

Answer : How to control growing size of an MSSQL database transaction log file

I thought you did not want to implement a new framework?

If you are trying to implement a framework, then you should go ahead and research them and choose one.   If you want my opinion on frameworks, I would consider simply posting each page to itself.   It's very easy and more powerful than many frameworks for error handling.  You can organize and share code using cfinclude for update statements and such.   Keep it simple!


But what you said was, you wanted to implement ONE PAGE of a framework (fusebox) and NOT the entire site.  

My comment is that this is not a good idea.   There is no real way to implement one page of fusebox.  It's easy enough to take the switch statement and put it at the top of your form and submit the page to itself.   Don't try to implement one page of a framework.

If you post the code, I can show you what I mean.