The first thing that occurs to me it's: I think 20 minutes could be ok because we are talking about one SP that will do 700.000 posts inside the same transaction. When you commit, the server must handle this large amount of data in one single commit.

Could you break the SP do to it in parts? Something like 'do 50,000 rows and return so I can commit'? Maybe using IDFirst, IDLast as a parameter. Just to try if could be something related to this.

Artur

----- Original Message -----
At 24/02/2002 05:51 PM, you wrote:
>I have sp, that walks through a table with 700.000 rows and for every
>row I do some calculations and write the result in another table. After
>executing the sp and commiting the transactions it takes up to 20
>minutes to disconnect from the server. I use localconnection and IB
>6.02.
>Any ideas ?

Is ForecedWrites=ON or OFF?

If I'm not mistaken, when it's OFF the server has to save all the data that
is in memory to the HD. I think this happens if you are the last one
disconnecting from the server. I know this is a downfall for IB or FB
running on Windows systems for the moment. I sent a suggestion for FB a
while back on what to use, but for IB, it's upto Borland to find their
solution to the problem if they acknowledge it. With Linux the problem
doesn't exist, because it writes to the HD when it's in idle mode(that what
was thought of for Windows too).

With ForcedWrites=ON, the changes are made to the HD as they are sent to
the database.

Daniel Rail
Senior System Engineer
ACCRA Group Inc. (www.accra.ca)
ACCRA Med Software Inc. (www.accramed.ca)



[Non-text portions of this message have been removed]