Anjula (an********@hotmail.com) writes:
I am doing updates in my stored procedure. I have one update in one
transaction.
I checked my transaction log space before I ran this proc and I had
enough room for it to grow. Sometimes this proc runs fine and
sometimes I get the above error.
Apparently there was not enough with space for it to grow. I would
expect that a procedure that runs for 18 hours incurs quite a strain
on the transaction log. Note also that other updates that takes place
while the procedure is running will also take up space in the log.
Not knowing anything about your application, I can only give general
advice such as investigate whether you can break up the transaction in
smaller parts without violating data integrity.
Also, you should investigate which recovery mode you are using, and
if you are running with full or bulk-logged mode, if you can increase
how often you back up the transaction log.
--
Erland Sommarskog, SQL Server MVP,
so****@algonet.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp