Database mirroring: avoiding ‘cannot obtain a LOCK resource’ problems

This is an interesting case that came up recently, and that I’ve seen a few times before, but which I haven’t seen explained anywhere. Using database mirroring, you may see 1204 and 1454 errors on the mirror server with no other databases or activity on the mirror server apart from database mirroring: With no activity […]

Max server memory configuration survey results

A long time ago, in a galaxy far, far away I kicked off a survey about memory configuration. Actually it was back at the start of January and I've been terribly remiss about posting the survey results! I was interested in how the setting of Max Server Memory (which controls the maximum size of the […]

Survey: memory configuration

Time for another survey – this time around memory configuration. Here is some code to run if you're on SQL Server 2008 and 2008 R2 (thanks Jonathan!): SELECT     [physical_memory_in_bytes] AS [PhysMemBytes],     [physical_memory_in_use_kb] AS [PhysMemInUseKB],     [available_physical_memory_kb] AS [PhysMemAvailKB],     [locked_page_allocations_kb] AS [LPAllocKB],     [max_server_memory] AS [MaxSvrMem],     [min_server_memory] AS [MinSvrMem] FROM     sys.dm_os_sys_info […]

Performance issues from wasted buffer pool memory

Back in April I kicked off a survey where I asked you all to send me some information about your buffer pools – how much memory is being used for data file pages and how much of that memory is storing empty space. I got back data from 1394 servers around the world – thanks! […]

A SQL Server DBA myth a day: (5/30) AWE must be enabled on 64-bit servers

(Look in the Misconceptions blog category for the rest of the month’s posts and check out the 60-page PDF with all the myths and misconceptions blog posts collected together when you join our Insider list, plus my online Myths and Misconceptions training course on Pluralsight.) Myth #5: AWE must be enabled on 64-bit servers FALSE […]

TechNet Magazine: October 2009 SQL Q&A column

(First blog post from Poland! We're here to present at the Microsoft Poland Technology Summit.)  The October edition of TechNet Magazine is available on the web now and has the latest installment of my regular SQL Q&A column. This month's topics are: Unexpected consistency checks? How much space is each database using in the buffer […]

Memory: Large Pages and MemToLeave

I'm constantly surprised by the number of people that don't follow the CSS SQL blog – some of the best SQL people in the industry post there. I just revisited a couple of really interesting posts by my good friend Bob Ward on memory management internals that I'd like to publicize. The first (from June […]

Don’t confuse error 823 and error 832

I was reading a thread on SQL Server Central today where someone replied to a question and confused 823 with 832. Now, 823 is a nasty error to get – it says that an I/O operation failed at the OS level and the I/O subsystem is causing corruption – SQL Server didn't even get a […]

Blog series on computer memory architectures

(Thanks to David Baffaleuf for pointing this out to me) Ever wanted to know a bit deeper how memory works in your laptop or servers? This comprehensive series of blog posts will give you a great overview. It's very clearly written and goes very deep. At times it talks about how things show up in […]

MS announces support for ‘lock pages in memory’ for Standard Edition

Finally! All those customers out there who are frustrated by not being able to turn on the 'lock pages in memory' option to protect the SQL working set on Standard Edition – the wait is nearly over. Bob Ward (Principal Escalation Engineer in CSS, and a good friend of mine) announced at PASS Europe that […]