Does anyone know exactly what behaviour is exhibited when running a
stored procedure and the log file fills up while the procedure is still
running?
I am seeing, through a created history table, a stored procedure that
began to run (by the fact that there is a row in the history table) but
not finish correctly. It is being called by VB and no user is
reporting that VB is erroring out.
Checking some of the SQL log files, the times the SQL proc bombed is
around the same time the SQL transaction log had to be manually dumped
because it was full.

Thanks,

(steven.cooper@infocision.com) writes:
> Does anyone know exactly what behaviour is exhibited when running a
> stored procedure and the log file fills up while the procedure is still
> running?

Sounds like that stored procedure is making a lot of updates, and eventually
the log fills up. Is your database running in simple recovery mode, or
in bulk-logged/full mode?

> I am seeing, through a created history table, a stored procedure that
> began to run (by the fact that there is a row in the history table) but
> not finish correctly. It is being called by VB and no user is
> reporting that VB is erroring out.

Looks like you should check whethert the error handling in the VB is
appropriate.




--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp