No news isn’t good news: sometimes it’s terrifying. Just because your SQL Server slaves away silently doesn’t mean all is well. If you’re frustrated with your server’s performance and you’re not sure why things aren’t going faster, maybe there’s a hidden hazard holding you back. In this session, Brent will demonstrate a few of the top server issues he sees out in the wild, explain how to monitor for them, and show you where to go to learn how to fix them for good. If you’re an accidental DBA or a developer stuck managing a SQL Server that scares you, gain confidence in this challenging session:

If you’re in Chicago, join me for free on October 5th to hear even more in person.  I’m speaking at Red Gate SQL in the City, an all-day event at the Field Museum in downtown Chicago.  They’ve put together an awesome agenda with big-name speakers like Grant Fritchey, Steve Jones, Allen White, and my own coworker, Jes Schultz Borland.  It’s a lot of free learning – and they’re doing more in New York, Austin, San Francisco, Chicago, Boston, and Seattle.  Register now for one near you.

And of course, you can see a lot of scary surprises inside your SQL Server by using our free sp_Blitz®.

Brent Ozar
I make Microsoft SQL Server faster and more reliable. I love teaching, travel, and laughing.

I’m mostly a figurehead here at Brent Ozar Unlimited. My true skills are menu advice, interpretive dance, and reading Wikipedia.
Brent Ozar on sabtwitterBrent Ozar on sablinkedinBrent Ozar on sabinstagramBrent Ozar on sabgoogleBrent Ozar on sabfacebook
↑ Back to top
  1. Pingback: Stop Copying Files from the Server – File Cache Bug « Voice of the DBA

  2. Pingback: Something for the Weekend - SQL Server Links 07/09/12

  3. Hi Brent,

    Another great webcast. Thanks for sharing all this great info that allows a dumb sysadmin like me look like a competant DBAdmin!

    Our SQL server suffered from the free memory problem so this video was most interesting. After a reboot, the free RAM went from 3GB to 0 in a few hours. No RDP or filecopy involved, honest! RAMMap confirmed there was no problem with Metafile data. All our free RAM seemed to be in the Mapped File – Standby column.

    There’s an app on the server tracking licence usage of our ERP (has to be on the database server) that creates small file, one for each login in a log directory. When the login was finished, the file was not erased. This app over the last year had created 20,000 small files. After a reboot, the first login causes the server to cache every file in that folder and that ate all our RAM. Delete all the stale files and we’re back in business and humming! Thanks for setting me on the right track to solve this problem.

    Dave Bragg

  4. Brent,
    Caught your session in Chicago, and already started making waves back at work with the file cache issue. We’re a small company, supporting a couple of SQL based applications that get installed at the client sites, and have for the longest time done all our management via RDP.
    Now, I’m looking at ways for the staff to continue to be able to support the apps, without logging in directly, or if they do, how to release the RAM when they’re done (which so far will likely end up being a scheduled task to reboot the server during downtime {which we can do because these aren’t [thankfully] 24×7 systems}) Not a perfect fix, but if it were a perfect world, Windows would let go of the RAM eventually…

    Thanks again,
    Jason A.

  5. I attended this session in Seattle today. Wow! fantastic presentaion! Your talk made me think about the temp db and “what is the right way to set it up?” What resources would you recommend for the Dev who has very little Formal DBA training on the right way to set up a SQL server?

  6. We have problems in page file… Leave no available pagging place….
    We do not know what to do…..

  7. I can’t say I’ve seen any problems with excessive caching of the [i]contents[/i] of files on any of the thousands of Windows Server 2008 and 2008 R2 machines I administrate. However, I have seen lots of problems with undesirable caching of large amounts of file system metadata, typically giant MFTs on machines with millions of files (this is easy to identify with Sysinternals RAMMap). There is probably documentation from MS that I should be citing to support this, but my point is that I suspect the distinction is getting overlooked in parts of this video.

Leave a Reply

Your email address will not be published. Required fields are marked *