I have an ACT! professional for Windows V11.1, with the latest SQL service pack (SP3) and have an apparent memory leak on the server.
After a restart the ACT! SQL instance (SQLSERVR) consumes almost all the available memory on the server, we have added more memory to the server (it is running under Hyper-V) but it continues to consume it all.
I have not been able to connect to the SQL server instance using management studio in order to limit the amount of RAM it is allocated.
Are there any potential solutions for this? or should I continue to restart the services?
Not a memory leak, but standard behavior.
How to configure SQL Server max memory usage
SQL SERVER 2008 - Memory Leak while storing Millions of records
+ this excellent blog entry
Other than that...
x86 or x64?
Server RAM?
PAE/AWE/3GB switch
DB size?
(left field) Trace flag 836 (changes 32 bit memory to act like SQL 2000)
Related
Recent days, in our organisation, we are facing with a strange issue.
Our SQL Server has enough memory(256 GB) and CPU cores. There is no memory pressure(outcome of dm_os_sys_memory is "Available physical memory is high").
Only problem is, the procedure stats sys.dm_exec_procedure_stats is getting cleared very often. Stats doesn't stay even for an hour.
The reason why we need the stats is, it is being collected on daily basis with the help of the DMV dm_exec_procedure_stats. And, our SQL Developers used to do optimization on stored procedures, and once it is done, to know the effectiveness of the tuning activity, a comparison is being done between the collected historical stats and the current one.
Since, the procedure stats is not staying on the cache, we are not able to set any benchmark.
Kindly suggest some solutions.
Version: Microsoft SQL Server 2017 (RTM) - 14.0.1000.169 (X64) Enterprise Edition: (64-bit) on Windows Server 2012 R2 Standard 6.3 (Build 9600: )
There are a number of ways that the cache can get cleared from Overall instance config changes to Db changes through to using recompile in procedures.
This link gives a good lead on what may be causing the issue but I think you are going to have to do some investigating.
https://www.sqlskills.com/blogs/glenn/eight-different-ways-to-clear-the-sql-server-plan-cache/
SQL Server Management Studio 2014 and is drawing over 1 GB memory every time it is launched. Often the program becomes unresponsive. Even when no queries are running. I was using it yesterday with no problems. I don't believe that I made any changes that would impact Management Studio. Any thoughts?
The observed problem and error message is:
The instance of the SQL Server Database Engine cannot obtain a LOCK resource at this time. Rerun your statement when there are fewer active users.Ask the database administrator to check the lock and memory configuration for this instance, or to check for long-running transactions
Environment: SQL Server 2005 Standard edition on Windows server 2003 Standard edition. Virtualized on a VM - with 8 GB RAM
Automatic applications are processing data - reading raw data and writing results to the database. These applications get the error message and they crash on it. (There are also database backup and index maintenance jobs scheduled.)
The same error was never observed on a similar system with sql server 2005 enterprise edition and windows 2003 enterprise edition.
I have already searched the web and found some answers. But e.g.
SQL Server cannot obtain a LOCK resource at this time - What to do?
was not helpful in my case
One source suggested to check:
SELECT request_session_id, COUNT (*) num_locks
FROM sys.dm_tran_locks
GROUP BY request_session_id
ORDER BY count (*) DESC
One session came up with 10.
The memory and lock settings are both in the default settings.
My current idea is to purge most of the data which is old and can be removed.
Does anybody have any other ideas how to deal with the lock resource problem? What exactly is its cause? Does SQL server standard edition allow less resources - is the problem related to the sql server version? How to fix the issue?
The autoshrink function had multiple locks on the database catalog.
The autoshrink also fragmented the primary key of a table after rebuilding the primary key.
Switching off the autoshrink function has solved the problem
We have a Windows 2008 Server R2 Enterprise x64 with 32gb.
We are also still using SQL Server 2000 Enterprise.
I have been monitoring the memory usage and it is only using 17.3GB total.
I have set SQL server to use AWE with a max memory usage of 29gb.
Any ideas how to allow/get SQL server to use the extra ram?
Thanks
The reason it is not using all memory is because it doesn't need it.
SQL Server is very good at managing it's own memory. The sizes of the databases you gave, fit into 11GB of RAM, that leaves 6.3 GB for internal structures such as buffers, plan cache etc. (more than enough).
I need an expert insight to my problem. most of my experience is development so i dont have enough grasp regarding server issues or maintenance. Main problem is when traffic is high request to this SQL server times out. there are several applications connecting to this server, some are web some are windows app. i would like to know if i need to do hardware upgrade(more ram, more hdisk space and how much of each is enough) or SQL server maintenance (rebuilding index, SP enhancement, denormalization etc.) or both?
OK first let me give you some specs of the server i'm having trouble with.
OS: MS Windows Server 2003 Standard
Version: 5.2.3790 SP 1 Build 3790
System Type: x64-based PC
Processor: EM64T Family 6 Model 15 Stepping 6 GenuinIntel ~2993 Mhz
RAM: 8gb
free C: space: 400mb
SQL Server Soft. Ver.: Sql Server 2005 Developer Edition
hope info above is enough for a diagnosis. my main concern initially is the available space in c:. also i'm looking at the RAM, i use perfmon and when traffic is high its reaching its max. as for CPU i have no idea but sometimes its running at 100% but its not always like that so i think its normal.
next question i think will be pointless because i cant give you sql db details but i will ask anyway. Will reindexing help or SP optimazation and to what extent? db is at 50+gb now
do we need a new server(hardware)?
Will Updating the sql server software help? from 2005 to 2008? is there an issue when your SQL server prod is only dev edition?
when you have an issue like this what could be the default fix or quick fix if there are any..
I hope an experienced Sys. Ad. or DBA or some programming god have pitty on me and enlighten me regarding this problem
Thanks in advance.
The first step would be to provide more useful information in your question. How does the server behave under pressure.
Use perfmon and or Sql Profiler http://msdn.microsoft.com/en-us/library/ms187929.aspx to log a number of data points while it is under load.
Also see Performance tuning with SQL Server and https://serverfault.com/questions/4700/how-to-do-periodic-sql-server-performance-monitoring-and-troubleshooting