Tag Info

New answers tagged

0

According to: How to reduce paging of buffer pool memory in the 64-bit version of SQL Server (http://support.microsoft.com/en-us/kb/918483) makes it appear that this is asynchronous: On a Windows Server 2003 or a Windows XP or later version system, SQL Server can use the memory notification mechanisms that are provided by the ...


2

Yes you are correct, from SQL Server 2005 onwards with arrival of SQLOS( actually it was called UMS in SQl Server 2000) Wiindows OS never directly asks SQL Server to trim down its memory consuption when OS is seeing memory pressure. Instead it raises flags(MEMPHYSICAL_HIGH and MEMPHYSICAL_LOW). These flags are monitored by SQLOS dedicated threads ,that in ...


2

@AaronBertrand's answer is great. Here's a variation with a bit more info from here SELECT (physical_memory_in_use_kb/1024) AS Memory_usedby_Sqlserver_MB, (locked_page_allocations_kb/1024) AS Locked_pages_used_Sqlserver_MB, (total_virtual_address_space_kb/1024) AS Total_VAS_in_MB, process_physical_memory_low, process_virtual_memory_low FROM ...


0

As the Danish physicist Niels Bohr once said, "Predictions are difficult, especially about the future!". :-) For starters, could you give us the RDBMS that you will be using? Secondly, this is a virtually impossible question to answer. What's the load on the system going to be? How many transactions/second? per minute/hour/day/week/month/year? You've got ...


0

1GB requires LONGTEXT or LONGBLOB. But that datatype may give you headaches. I suggest you experiment with one row with 1GB of data in a column declared LONGTEXT CHARACTER SET ascii. If it is just ASCII, then LONGTEXT makes sense. LONGBLOB would work very similarly. You will probably need to set max_allowed_packet. I have seen a few systems with it set ...


0

From SQL 2012 onwards, single_pages_kb got replaced by pages_kb in that DMV. https://msdn.microsoft.com/en-us/library/ms175019.aspx?f=255&MSPPError=-2147217396 So if you want to run the query included in the question, on a 2012+ server, remove the single_ string.


1

I wish the creator of that tool would toss that line. It unnecessarily scares people. And the number it gives is both too small and too large. But, in your case, it there is a real danger. If you had just 3 queries running that were nasty enough, they could be asking for 2.4GB -- more than your RAM!! This is because tmp_table_size and ...



Top 50 recent answers are included