Posted by sasachi sachi sachi on 02/11/06 05:38

Hi there,

I have a data manipulation process written in a Nested Stored procedure
that have four levels deeper. When I run these individual procedures
individually they all seems to be fine. Where as when I run them all
together as Nested proces (calling one in another as sub-procedures) Log
file is growing pretty bad like 25 to 30GB.. and finally getting kicked
after running disk space. This process is running around 3hrs on a SQL
serever Standard Box having dual processer and 2gb ram.

This procedures have bunch of bulk updates and at least one cursor in
eacch procedure that gets looped through.

I was wondering if anybody experienced this situation or have any clue
as to why is this happening and how to resolve this?

I am in a pretty bad shape to deliver this product and in need of urgent
help.

Any ideas would be greatly appreciated..

Thanks in advance


*** Sent via Developersdex http://www.developersdex.com ***

• Next in forum: Re: one for the SQL experts - dare I say TRICKY SQL!
• Prev in forum: Re: SQL Server 2K Linked Access 97 Server not working
• Thread view: Why the log file is growing too much upon running nested stored procedures (MS SQL 2K)

[Reply to this message]