Thank you very much for your reply.
We finally found that the stored procedure was opening a xml cursor with sp_xml_preparedocument and there was no corresponding sp_xml_removedocument. This was affecting performance of course after several thousands of times.

Thanks Chris.



>>I have been running different VFP processes on SQL server, but there is one specific where the windows task manager reports memory usage starting on 400,000 KB and going up to 1,500,000 (1.5GB) . Total physical memory is 4GB and this is a tests server only. Database size is about 2GB.
>
>Just wondering: If you reduce the SQL Server's allowed maximum memory, does this affect the memory used by the VFP-instigated process?
>
>(In Microsoft SQL Server Management Studio, right-click on the server in the Object Explorer. Select properties. Select Memory from the list on the left. Reduce the maximum amount of memory allocated to SQL Server. Restart the SQL Server process.)
>
>Are you using the latest SQL Server build, with SP1 (9.0.2047)?
>
>Among several other possible factors, performance of long-running processes can also be affected by the size of TempDB, how it is set up for autogrowth (or set to a static size), and its available room to grow.
>
>Chris