Hi!
Check how many users are connected to server simultaneously and check if transaction is finished correctly after each command sent to the SQL Server. Ofter long work you app might open a lot of handles to SQL Server when views do not use shared connection. When transactions managed inproperly, very long transaction is stored for all data updates and can cause overload too, but I'm not sure about the last one. Have no other ideas but posting this to SQL Server forum...
>Our VFP 6.0 app w/SQL 2000 backend will run ok for extended periods of time, then suddenly we get update errors saying SQL Server doesn't have enough memory to run the query (same queries it's been running all along). We go into Enterprise Manager, stop and restart the service and all is well again. Any ideas what causes this?
>
>TIA
Vlad Grynchyshyn, Project Manager, MCP
vgryn@yahoo.comICQ #10709245
The professional level of programmer could be determined by level of stupidity of his/her bugs
It is not appropriate to say that question is "foolish". There could be only foolish answers. Everybody passed period of time when knows nothing about something.
