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?
Related
Last weekend, we successfully migrated a SQL2016 AlwaysOnAG to a SQL 2019 AlwayOnAG. The new server has double the amount of memory (512GB), it's patched to CU12. OS is Windows Server 2019. Last night SQL crashed due to an "out of memory" error. As a result a failover took place. It looks like this error was caused by a rebuild of a columnstore index, because I saw a start of this action, but no completion time (we use the scripts from Ola Hallengren).
This index was already in the SQL2016 environment and no changes have been made since the migration (we're still in a "freeze"). Some things we are using: TDE, memory-optimized tempdb, in-memory tables, resource governor (disabled), polybase (but not used so far). Max memory for SQL is 448GB according to http://sqlmax.chuvash.eu/.
To me, an index rebuild should not result in this error. Any thoughts/ recommendations about this issue?
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/
We have 8 instances out of which 6 are SQL Server 2014, 1 is SQL Server 2017 and all servers are running on Windows Server 2012 R2. The min and max memory set correctly for SQL Server 2014 & 2017. However, one of our DBAs enabled lock pages in memory for SQL Server 2017, but rest do not have this counter enabled.
There is one instance which sometime run into a problem "insufficient memory to process the thread" on same box.
What would be the recommendation for lock pages in memory for server with multiple instances? Should we enable it or not, even if we set min and max memory correctly.
We recently moved from the following server: Windows Server 2008 R2 + MSSQL 2008 R2 STD to Windows Server 2012 R2 +MSSQL 2016 STD. In terms of hardware, the old server was 1271v3 with 24 GB memory and the new server is 1271v6 with 32GB of memory. The rest of the hardware of the two servers is the same. The db was transferred using db backup and restore.
Although everything is working on the new server with no errors, it is significantly slower than the original server and we are even seeing some deadlocks.
If everything is the same or newer/better, how can this be?
The problem was not SQL server at all. The new server was using the default Windows power plan which is "Balanced". Switching the plan to "High Performance" mode caused a performance increase of up to 300% on more complex and long running queries.
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)