SQL 2019- Max DOP and Memory Configuration

By | November 17, 2019

Probably the most useless recommendation and as far as I am concerned not a feature. Why?

If you are a DBA you know that DOP and Memory limits are fine-tuned based on the workload and system details. Things like concurrency OLTP vs OLAP, usage of in memory vs traditional tables Buffer pool extensions, number of instances, virtualization and many more parameters dictate these settings. And it’s part of every DBAs post install checklist. So should you use these settings in real life? NO!

What if it’s for quickly setting up dev and test environments?

Even then you shouldn’t rely on this screen instead you should be making these changes are part of your post install checklist so that the process remains the same no matter what the version of SQL is.

MAXDOP Settings

Memory Configuration Settings

Category: Databases

About opsadmin

This post was written by Jayanth Kurup. A Microsoft SQL Server Consultant and Trainer based out of Bangalore, India. Jayanth has been working on MS SQL Server for over 15 years. He is a performance tuning and Business Intelligence expert. Having worked with companies like Microsoft, DELL, Wells Fargo, Thomson Reuters and many other fortune 100 companies. Some other technologies Jayanth works on include Microsoft Azure, PowerBI, Python and AWS. When he isn’t consulting or training, Jayanth like to travel, paint and read. He is also very active in social causes and the founder of Enabled Business Solutions. Visit his company by clicking the link in the menu or email him directly.