General information
Forum:
Microsoft SQL Server
Title:
Transaction Logs getting filled up quickly
Hello,
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.
Thanks for your help.
Alvin
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only