Hi Alvin,

You can find answers to some of your questions in Truncating the Transaction Log in BOL.

>
>I have an online application that performs a large number of transactions per day.
>
>I noticed yesterday that while executing a stored procedure the application suddenly just stopped working. After further investigation, I realized that the transaction log was full and the application was unable to write to the log therefore causing the application to do nothing.
>
>Question:
>
>What is the best way to truncate the transaction logs? ie... SQL Job? Query?
>Is there a query to do this or does this have to be done using Enterprise Manager?
>This is probably a dumb question but does truncating the transaction log while a stored procedure or process is being executed on the server cause errors or data consistency issues.
>