Database Research & Development

  • Home
  • NoSQL
    • NoSQL
    • Cassandra
  • Databases
    • Database Theory
    • Database Designing
    • SQL Server Coding Standards
    • SQL Server
    • PostgreSQL
    • MySQL
    • Greenplum
    • Linux
  • Interviews
    • SQL Server Interviews
    • MySQL Interviews
    • SQL Puzzles
  • DBA Scripts
    • SQL Server DBA Scripts
    • PostgreSQL DBA Scripts
    • MySQL DBA Scripts
    • Greenplum DBA Scripts
  • Home
  • Blog Archives !
  • (: Laugh@dbrnd :)
  • Contact Me !
sqlserverinterviews
Home 2018 January SQL Server 2016: Introduced Database Scoped Configuration Options

SQL Server 2016: Introduced Database Scoped Configuration Options

SQLScope

This article is half-done without your Comment! *** Please share your thoughts via Comment ***

SQL Server 2016 introduced Database Scoped Configuration Options that can set at the database level, which was previously available at the instance level only.

In SSMS, you can right click on database -> go to -> option -> find Database Scoped Configuration section.
It introduced main four parameters, which we can set at the database level.

Legacy Cardinality Estimation: It enables you to configure the query optimizer cardinality estimation model.

MAXDOP: Maximum degree of parallelism for an individual database.

Parameter Sniffing: Previously, we can disable this feature using trace flag 4136, but now you can ON/OFF Parameter Sniffing at the database level.

Query Optimizer Fixes: You can enable or disable query optimization hotfixes.

Clear Database Plan: It allows clearing procedure cache at the database level without impacting other databases.

SQL Server 2016 also introduced one DMV to check the current value of Database Scoped Configurations.

1
SELECT *FROM sys.database_scoped_configurations

Database user requires Scoped Configuration permission to execute ALTER SCOPED CONFIGURATION.

1
GRANT ALTER ANY DATABASE SCOPED CONFIGURATION to UserName;

Related T-SQL Scripts:

Clear atabase Plan Cache:

1
ALTER DATABASE SCOPED CONFIGURATION CLEAR PROCEDURE_CACHE;

Enable Legacy Cardinality Estimation:

1
ALTER DATABASE SCOPED CONFIGURATION SET LEGACY_CARDINALITY_ESTIMATION = ON;

Set MAXDOP Value:

1
ALTER DATABASE SCOPED CONFIGURATION SET MAXDOP = 3;

Disable Parameter Sniffing:

1
ALTER DATABASE SCOPED CONFIGURATION SET PARAMETER_SNIFFING = OFF;

Enable Query Optimizer Fixes:

1
ALTER DATABASE SCOPED CONFIGURATION SET QUERY_OPTIMIZER_HOTFIXES = ON;

Jan 4, 2018Anvesh Patel
SQL Server 2014: Monitor Memory Optimized Tables which stored in MemorySQL Server 2016: Introduced MAXDOP with DBCC Commands

Leave a Reply Cancel reply

CAPTCHA
Refresh

*

Anvesh Patel
Anvesh Patel

Database Engineer

ImageJanuary 4, 2018 SQL ServerAnvesh Patel, cardinality, database, database plan, database research and development, dbrnd, Genetic Query Optimizer, MAXDOP, Parameter Sniffing, scoped configuration, SQL Query, SQL Server, SQL Server Administrator, SQL Server Monitoring, SQL Server Performance Tunning, SQL Server Tips and Tricks, TSQL
About Me!

I'm Anvesh Patel, a Database Engineer certified by Oracle and IBM. I'm working as a Database Architect, Database Optimizer, Database Administrator, Database Developer. Providing the best articles and solutions for different problems in the best manner through my blogs is my passion. I have more than six years of experience with various RDBMS products like MSSQL Server, PostgreSQL, MySQL, Greenplum and currently learning and doing research on BIGData and NoSQL technology. -- Hyderabad, India.

About DBRND !

dbrnd

This is a personal blog (www.dbrnd.com).

Any views or opinions represented in this blog are personal and belong solely to the blog owner and do not represent those of people, institutions or organizations that the owner may or may not be associated with in professional or personal capacity, unless explicitly stated.

Feel free to challenge me, disagree with me, or tell me I’m completely nuts in the comments section of each blog entry, but I reserve the right to delete any comment for any reason whatsoever (abusive, profane, rude, or anonymous comments) - so keep it polite.

The content of this website is protected by copyright. No portion of this website may be copied or replicated in any form without the written consent of the website owner.

Recent Comments !
  • Anvesh Patel { Sure will do... } – May 27, 12:43 PM
  • Anvesh Patel { Great... } – May 27, 12:41 PM
  • Anvesh Patel { Great... } – May 27, 12:39 PM
  • Anvesh Patel { Great... } – May 27, 12:36 PM
  • Anvesh Patel { Great... } – May 27, 12:28 PM
  • Anvesh Patel { Great... } – May 27, 12:27 PM
  • Anvesh Patel { Great... } – May 27, 12:16 PM
  • Older »
Follow Me !
  • facebook
  • linkedin
  • twitter
  • youtube
  • google
  • flickr
© 2015 – 2019 All rights reserved. Database Research & Development (dbrnd.com)
Posting....