I am fairly new to SQL Server but have a lot of experience with Oracle. I am trying to set up a backup plan for a transaction processing based SQL Server database. With Oracle, the transaction logs can automatically be archived (backed up). Apparently with SQL Server, the transaction logs are archived via the backup/maintenance plan and are cleared out when a backup is performed. However, if I restrict the size of the transaction log file, is it purely a matter of knowing how much transaction space is used by my database to determine how often the backup of the transaction logs has to take place? This seems sort of strange to me because you could have an anomolous large transaction that could cause your database to come to a screeching halt. Also, how do you tell how large your transaction logs should be? Simply by allowing them to grow for a period of time and seeing how large they get and then limiting them to that size? Seems kind of a strange way to do it. Any input on this is appreciated.