About SQL Server memory issues (Favorites)

server|sqlserver| problem Http://www.richsearch.com/search/search.aspx?page=1&S1=%2B%E5%86%85%E5%AD%98%20%2B "sql% 20Server "
Allocate more memory to SQL Server (the default is dynamic allocation, you can change the minimum value to a larger data).
View the log file and data file size of the database and adjust it appropriately.
-----------------
The insertion record is slow, possibly because the table uses a clustered index, and new records cause a change in the storage location of a large amount of data.
http://www.delphibbs.com/delphibbs/dispq.asp?lid=2037790


From: Shaoyy, Time: 2004-5-31 9:25:00, id:2636792 [show: Small font | Big Font]
My company's a POS system, the background is SQL Server, the front desk is ADO, now is ado+midas,2 years often will appear this problem: when the system is busy (when the business is good), SQL Server will change no response, and then all the front desk panic, One months will appear one or two times, looking for a long time, do not know whether it is SQL Server or program problems? If you have any experience in this field, but also hope that the generous enlighten, give some hints, thanks!
http://www.delphibbs.com/delphibbs/dispq.asp?lid=2636792


The database has the ability of self-regulation to a large extent. As memory grows, SQL Server expands memory footprint, and SQL Server frees up some of the memory space when memory pressure from other applications increases. Similarly, SQL Server will dynamically expand or shrink database and log space based on actual needs.
Http://www.microsoft.com/china/technet/prodtechnol/sql/2000/plan/ssmsam.mspx


By the way I do securities software, the volume of data is generally greater than 100 million, SQL Server often eat 2-4g memory
But the system works well.

Actually, it's not that simple.
MSSQL is problematic in the release of memory.
If it is really massive data (the so-called mass, not only one hundred or two hundred G concept), you will find that, in
A short period of time, if contacted for a large number of inquiries and other operations, it
The memory will continue to rise, then the speed of the database will be significantly reduced,
Often at this time, if you reboot the system, you can solve the problem.
Contacted with Microsoft, there is no good solution at the moment.
Later, we made several components to improve its efficiency, although not very good, but acceptable.
Like the database this thing, especially MSSQL, in the case of large amount of data, it really does not use.
But because it's better connected to Microsoft's own operating system, well,
So I had to use his.
http://www.delphibbs.com/delphibbs/dispq.asp?lid=1775126


Instead of Oracle.
http://www.delphibbs.com/delphibbs/dispq.asp?lid=287033


Server memory is 1G, two days after the Task Manager observation, the use of memory has been occupied by more than 900M,
The thread sqlservr takes up the most and the number of customer connections is only few.
http://www.delphibbs.com/delphibbs/dispq.asp?lid=2144996


The following article may help you:
Http://www.ck23.com/net/html/2003-7-27/2003727151935.htm
Do not use server-side cursors in Delphi, or you will soon run out of memory on your server.
http://www.delphibbs.com/delphibbs/dispq.asp?lid=2144996


As mentioned earlier, this is the advantage of SQL Server, because it provides buffer memory, even if the user temporarily offline,
It also does not release all caches.
Of course, it does not consume memory until it detects that the operating system does not allocate enough memory, it
Timely release of memory, do not believe you can be so detected, users offline, running Photoshop on the server side to occupy
The system memory is larger than the software test to ensure that at this time SQL Server will release some memory.
http://www.delphibbs.com/delphibbs/dispq.asp?lid=2353948