12 December,2013 by Jack Vamvas

With every version of SQL Server , the default values get better. Since SQL Server 2005 – one of things I’ve found impressive is the default values on SQL Server.  As with most technology – the default values are great for 99% of the users – but there are always DBAs who want to break the  speed limit.

 Read more on SQL Server has good default values 

When completing a SQL Server health check – one check is to review the types of default values a DBA will attempt – in the ultimate search for the “sweet spot”.   

I’m never surprised to see these default values changed : , awe enabled, Database Mail XPs, max server memory, min server memory.

 When I start seeing : xp_cmdshell  or Max Degrees of Parallelism changes I become nervous and begin to question more in-depth.

Before making any changes to sp_configure default values – consider the consequences and test thoroughly

 Check sys.configurations to review settings


Author: Jack Vamvas (http://www.sqlserver-dba.com)


Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Your comment could not be posted. Error type:
Your comment has been posted. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.


Post a comment on Sp_configure

sqlserver-dba.com | SQL Server Performance Tuning | SQL Server DBA:Everything | FAQ | Contact|Copyright & Disclaimer