SQL Database Recovery Tool

Bulk Logged will not help you in this situation. Your transaction log is growing because you are performing large transactions. In simple mode, the log is truncated after a checkpoint.
Check these site: http://www.sql.recoverytoolbox.com/ & download demo Recovery Toolbox for SQL Server.
Depending on how you are loading your data, you may need to break it up into smaller chunks. Make sure you are not loading all the data in one large transaction.
Read more: http://www.filerepairforum.com/forum/microsoft/microsoft-aa/sql-server/380-is-it-good-idea-to-change-simple-recover-model-into-bulk-logged-on-etl-system

Take a look at this video

An easy way to transfer objects (tables, user defined functions, stored procedures, etc.) is to use Enterprise Manager's "Generate SQL" feature. Use this process at your own risk. Doing it wrong could mess up your existing database.

1. In Enterprise Manager, right-click on the old database and choose "All Tasks" then "Generate SQL Script".
2. In the dialog that comes up, click "Show All" then select the checkboxes for "all stored procedures" and "all user defined functions". (You might also want to check some other boxes, depending on your exact situation.)
3. Click the "generate" button and save the script that it creates.
4. Run the script in the NEW database.

If you run the script in your OLD database, it may destroy your objects, and that would be very bad. Make sure you run the script in your NEW database. (While we're on this subject, it's a good time to mention that you should back up your database before you start this process, and you should make changes to a test system before migrating it to production.)

That should move your stored procedures and user defined functions over.

You can use a similar process to move tables, views, users, and other objects over as well.