Tag Info

New answers tagged

1

From SQL 2012 onwards you could look for a large discrepancy between SerialRequiredMemory and SerialDesiredMemory, eg something like this: -- Search plan cache for Memory Grant issues IF OBJECT_ID('tempdb..#tmp') IS NOT NULL DROP TABLE #tmp -- Collect more info about the plan here if required, eg usecounts, objtype etc, SELECT IDENTITY( INT, 1, 1 ) rowId, ...


10

This is a bug in SQL Server (from 2008 to 2014 inclusive). The filtering condition is pushed down into the scan operator as a residual predicate, but the memory granted for the sort is erroneously calculated based on the pre-filter cardinality estimate. To illustrate the issue, we can use (undocumented and unsupported) trace flag 9130 to prevent the Filter ...


0

The application now is stable again. As a first step the innodb_thread_concurrency was reduced 2 * number of cores. That seems to reduce the problem slightly. But in the end the statement that the Magento-Shop has issued has been replace by a simpler statement that is adequate for the special situation of the concrete shop. The shop uses only one ...


5

I did not find correct answer posted so I will try to explain you in details, bear with me. First whenever you post question please post version and edition of SQL Server you wont believe answer might change completely with different versions Lately we've noticed the VM Committed memory space for our SQL Server 2005 instance grows and it's almost at the ...


0

Could you post the following result from the Query?These points I have provided below may help you diagnose the issue Script to report Memory usage details of a SQL Server instance Original Author Sakthivel Chidambaram This Script will help you to diagnose the issue ...


1

Start by checking max memory. Instructions here: http://technet.microsoft.com/en-us/library/ms191144(v=sql.90).aspx You should set the max to be low enough to leave space for the os and any other apps. Which in your case is going to be very low. Maybe 500mb-1gb


7

The 64GB limit (and 128GB in 2014) applies only to buffer pool. The KB article "Memory configuration and sizing considerations in SQL Server 2012" says: Starting with SQL Server 2012, these memory limits are enforced only for the database cache (buffer pool). And as we all know, max server memory also does not control all of SQL Server's memory. The ...


3

Per Aaron Bertrand's answer (Quick look at how much RAM is allocated to SQL Server?). Task Manager shouldn't be used to ascertain how much memory SQL is actually using. I prefer to use the following query (Again, thanks Aaron): SELECT object_name, cntr_value FROM sys.dm_os_performance_counters WHERE counter_name IN ('Total Server Memory (KB)', 'Target ...


2

Before I start, I am proponent of FIXING MAX SERVER MEMORY always 1. I will first address SQL Server versions before SQL Server 2012. That means if you are using SQL Server 2005, SQL Server 2008 and SQL Server 2008 R2 (no I will not include SQL Server 2000) If you are using SQL Server version before 2012 and your operating system is Windows Server 2008 R2 ...


2

Generally speaking, no, there is no detrimental effect from maxing out memory once the OS and other applications have been accounted for. This is exemplified through the default settings of SQL Server: The default setting for min server memory is 0, and the default setting for max server memory is 2147483647 MB. SQL Server Memory Configurations (MSDN) ...



Top 50 recent answers are included