Transaction log question

[OldSkoolSkater]

Hi All

Having being thrown into SQL at the deep end, I am trying to get my head around backing up databases. I have browsed around and come up with the following strategy for my company:
Sun/Wed - Full backup
Mon/Tue/Thur/Fri/Sat - Differential backup
Every hour - Transaction log backup
I understand that if my database dies, I restore the full or differential backup first, and then restore all the Transaction log backups up to the point in time that the database died.
I chose to overwrite the transaction log backup initially, but soon realised that I would only ever have one backup.
If I choose to append the transaction log backup, I will have all that is required to restore to a point in time, but the backup will grow in size rapidly.
Is there a way of restricting the backup file size to 24 appends (ie. a day), thus enabling me to restore to a point in time without the backup file going huge??

Yours Confusedly

Steve

 

[tlbroadbent]

Which version of SQL Server are you running?

You can use the INIT option on the first transaction backup of the day to restart the file.

In SQL 7 and 2000, you can create a maintenance plan that will append the date/time to the transactionlog backup file name. You would get a new file for each backup. You can also set the option to delete the backups after a given time has passed. Terry L. Broadbent
faq183-874 contains some tips and ideas for posting questions in these forums. Please review it and comment if you have time.
NOTE: Reference to the FAQ is part of my signature and is not directed at any individual.