Free Webcast: DBA vs Memory Settings
Join me in two weeks for a really fun free webcast.
Join me in two weeks for a really fun free webcast.
A while back, I got a question about enabling SQL Server’s ‘Optimize for Adhoc Workloads’ setting. The gist of the question was whether or not enabling this setting might free up extra memory on their SQL Server instance.
Does your team know what it’s doing with SQL Server?
Learn what a consultant looks for when assessing a team, and signs that SQL Server may be badly configured.
Update, 6/21/2016: Be careful using indirect checkpoint with failover clusters if your SQL Server 2014 instance is not fully patched. See KB 3166902. This bug was fixed in SQL Server 2016 prior to RTM.
SQL Server 2016 introduces big new features, but it also includes small improvements as well. Many of these features are described in the “It Just Runs Faster” series of blog posts by Bob Ward and Bob Dorr.
Part of this past week I’ve spent doing a new SQL Server 2008 R2 installation and configuration on a Windows 2008 R2 cluster. I haven’t done an install end-to-end in quite a while– I have teammates who take care of it while following our installation checklist document.
When setting up data collection using the GUI, configuration failed halfway through setup. At the point of failure I found there were SQL Agent jobs for collections visible, but nothing appearing in Management Studio under Management\Data Collection. The Data Collection icon still had the ‘off’ down red arrow. (I manually refreshed it for good measure to make sure.)
There are a couple of local security policy rights that are not granted by default in SQL Server setup that I’ve been setting manually for a few years now:
Copyright (c) 2025, Catalyze SQL, LLC; all rights reserved. Opinions expressed on this site are solely those of Kendra Little of Catalyze SQL, LLC. Content policy: Short excerpts of blog posts (3 sentences) may be republished, but longer excerpts and artwork cannot be shared without explicit permission.