Transaction Logfile Maintenance suggestions
Posted on 2006-04-26
I'm a network administrator, and I have a programmer who works under me that has written a Real Estate listing search/Statistical package for which the database is MSSQL 2003.
The transaction logs regularly climb over 12-15gb and I end up having to detach and reattach the database so I can delete the transaction log to free up hard drive space.
My programmer tells me that this is 'normal' and that if I use the 'restrict filegrowth' option, the DB will stop working correctly once it reaches that allotted size. I suspect this is probably not true, but I don't want to risk it.
My question is, is there a way to set up a job within SQL server to delete that transaction log and recreate it once it reaches an allotted size? I don't see any way to do it. Is there even any reason to create a transaction log? Does SQL actually need it for anything?
Sorry if I seem ignorant here, but I just dont know that much about it.