>>I had similar problemms when testing MS SQL Server 6.5. What I found in reviewing the memory usage during updates and inserts that MS SQL Server was not releasing the memory. This resulted in a continual slowdown of the processes and lock up of the system. Then a re-boot of the system was required to release the memory. Because it was a memory leak (just a guess on my part) closing down MS SQL did not free up the memory. Since then I have tested and purchased ORACLE. This does have any memory leaks will stay a flat line during the processes I have tested and I have not re-boot the computer for weeks.
>
>
>This is not normal. There is a problem with either install or configuration.
I think I'd have to agree. We've been running SQL Server 6.5 for a while and have not had any problems. One app is a shuttle between our AS-400 and a web server, and the '400 has tanked more than anything.
Am currently working on a VFP front-end to SQL server. Going into beta this week. Should know in a hurry if there is a problem.
It is also my understanding that SQL Server/Windows NT is hardware-sensitive. I'm not a hardware jockey, can anyone confirm that?
Dan LeClair
www.cyberwombat.comSET RANT ON - The Wombat BlogLife isn’t a morality contest and purity makes a poor shield. - J. Peter MulhernDisclaimer: The comments made here are only my OPINIONS on various aspects of VFP, SQL Server, VS.NET, systems development, or life in general, and my OPINIONS should not be construed to be the authoritative word on any subject. No warranties or degrees of veracity are expressed or implied. Void where prohibited. Side effects may included dizziness, spontaneous combustion, or unexplainable cravings for dark beer. Wash with like colors only, serve immediately for best flavor.
