App design help: MS SQL Server logs growing too much

I have an application? which causes the SQL server transaction log to grow excessively. I need someone with MS SQL Server ? \**\*|\*EXPERT\**\*|\* knowledge to look at the stored procedures, database structure, SQL server traces, etc, and determine the cause of the problem + propose a solution and prove it's effectiveness. I can provide access to the whole db structure but I can not provide access to the client application code or excecutable. You can have full access? to the sql tables, traces, etc. Mainly what happens is described here <[login to view URL]> except that no errors are thrown. Everything seems to work just fine, except that the log file grows to 10 times of the size of the database file. The solution should be a redesign of the stored proocedures rather than implementing a schedule task to run log truncation commands, etc.