Is Using RECONFIGURE WITH OVERRIDE dangerous?

by Jan 13, 2013

Categories

Tags

Administration agent-based monitoring Agentless Monitoring alert responses alert thresholds alerting Alerts Amazon Aurora Amazon EC2 Amazon RDS Amazon RDS / Aurora Amazon RDS for SQL Server Amazon Redshift Amazon S3 Amazon Web Services (AWS) Analytics application monitoring Aqua Data Studio automation availability Azure Azure SQL Database azure sql managed instance Azure VM backup Backup and recovery backup and restore backup compression backup status Backup Strategy backups big data Blocking bug fixes business architecture business data objects business intelligence business process modeling business process models capacity planning change management cloud cloud database cloud database monitoring cloud infrastructure cloud migration cloud providers Cloud Readiness Cloud Services cloud storage cloud virtual machine cloud VM clusters code completion collaboration compliance compliance audit compliance audits compliance manager compliance reporting conference configuration connect to database cpu Cross Platform custom counters Custom Views customer survey customer testimonials Dark Theme dashboards data analysis Data Analytics data architect data architecture data breaches Data Collector data governance data lakes data lineage data management data model data modeler data modeling data models data privacy data protection data security data security measures data sources data visualization data warehouse database database administration database administrator database automation database backup database backups database capacity database changes database community database connection database design database developer database developers database development database diversity Database Engine Tuning Advisor database fragmentation database GUI database IDE database indexes database inventory management database locks database management database migration database monitoring database navigation database optimization database performance Database Permissions database platforms database profiling database queries database recovery database replication database restore database schema database security database support database synchronization database tools database transactions database tuning database-as-a-service databases DB Change Manager DB Optimizer DB PowerStudio DB2 DBA DBaaS DBArtisan dBase DBMS DDL Debugging defragmentation Demo diagnostic manager diagnostics dimensional modeling disaster recovery Download drills embedded database Encryption End-user Experience entity-relationship model ER/Studio ER/Studio Data Architect ER/Studio Enterprise Team Edition events execution plans free tools galera cluster GDPR Getting Started Git GitHub Google Cloud Hadoop Healthcare high availability HIPAA Hive hybrid clouds Hyper-V IDERA IDERA ACE Index Analyzer index optimization infrastructure as a service (IaaS) infrastructure monitoring installation Integrated Development Environment interbase Inventory Manager IT infrastructure Java JD Edwards JSON licensing load test load testing logical data model macOS macros managed cloud database managed cloud databases MariaDB memory memorystorage memoryusage metadata metric baselines metric thresholds Microsoft Azure Microsoft Azure SQL Database Microsoft PowerShell Microsoft SQL Server Microsoft Windows MongoDB monitoring Monitoring Tools Monyog multiple platforms MySQL news newsletter NoSQL Notifications odbc optimization Oracle PeopleSoft performance Performance Dashboards performance metrics performance monitoring performance schema performance tuning personally identifiable information physical data model Platform platform as a service (PaaS) PostgreSQL Precise Precise for Databases Precise for Oracle Precise for SQL Server Precise Management Database (PMDB) product updates Project Migration public clouds Query Analyzer query builder query monitor query optimization query performance Query Store query tool query tuning query-level waits Rapid SQL rdbms real time monitoring Real User Monitoring recovery regulations relational databases Releases Reporting Reports repository Restore reverse engineering Roadmap sample SAP Scalability Security Policy Security Practices server monitoring Server performance server-level waits Service Level Agreement SkySQL slow query SNMP snowflake source control SQL SQL Admin Toolset SQL CM SQL code SQL coding SQL Compliance Manager SQL Defrag Manager sql development SQL Diagnostic Manager SQL Diagnostic Manager for MySQL SQL Diagnostic Manager for SQL Server SQL Diagnostic Manager Pro SQL DM SQL Doctor SQL Enterprise Job Manager SQl IM SQL Inventory Manager SQL Management Suite SQL Monitoring SQL Performance SQL Quality SQL query SQL Query Tuner SQL Safe Backup SQL script SQL Secure SQL Security Suite SQL Server sql server alert SQL Server Migration SQL Server Performance SQL Server Recommendations SQL Server Security SQL statement history SQL tuning SQL Virtual Database sqlmemory sqlserver SQLyog Storage Storage Performance structured data Subversion Support tempdb tempdb data temporal data Tips and Tricks troubleshooting universal data models universal mapping unstructured data Uptime Infrastructure Monitor user experience user permissions Virtual Machine (VM) web services webinar What-if analysis WindowsPowerShell

One of my pet peeves is the use of RECONFIGURE WITH OVERRIDE in scripts to change server options. Am I being unreasonable or is this justified? All you need to do is look up the definition of the WITH OVERRIDE option for the RECONFIGURE command in Books Online to see where this particular peeve began.

 

WITH OVERRIDE: Disables the configuration value checking (for values that are not valid or for nonrecommended values) for the recovery interval advanced configuration options.

Let’s look at this definition in two parts:

1) Disables the configuration value checking (for values that are not valid or for nonrecommended values)

Does this mean that using WITH OVERRIDE will allow me to set any server configuration to an invalid value? No. Even with the override option, you can’t set a configuration option to a value outside of the defined minimum and maximum values. It also won’t override certain checks that prevent you from making configuration changes that would be dangerous to SQL Server like setting Max Server Memory to a value less than Min Server Memory. If you attempt this, the change will fail with an error stating that the defined value is not valid.

2) for the recovery interval advanced configuration options

Currently, the only option that is defined as being settable to a non-recommended or dangerous value is the Recovery Interval option that controls how frequently automatic checkpoints should occur. There are cases where this setting needs to be configured to a non-recommended value and the WITH OVERRIDE option is required to make that change. In fact, if you have this value already set to a non-recommended value, then you have to use the WITH OVERRIDE option on all future calls to RECONFIGURE even if that’s not the option being modified.

So if it’s just the one configuration, what’s so dangerous? The reason I think it is dangerous to just automatically use for everything is because it gives you no warnings at all that you are making a non-recommended change to a configuration. You could be trying to set it to a valid value and accidentally type in the wrong value, and you may never notice until you experience the downside caused by the change.

Additionally, what if they decide to add a new configuration option that can have value checking disabled and they forget to document it?

They wouldn’t do that, would they?

Surely Microsoft wouldn’t do something like add a new configuration option that allows disabling value checks and not document it or warn us. Would they? Well, in fact, they have done that very thing in SQL Server 2012. The contained database authentication setting in SQL Server 2012 can be disabled when there are contained databases present on the instance by using the WITH OVERRIDE setting. If you are using WITH OVERRIDE for all changes, you could make this change and not realize there are contained databases on the server because it makes the change without warning. Doing so will cause all contained users to be denied access to their databases.

Please help address this potential issue by voting for the following Connect bug/feature request. The Connect item requests that the behavior be changed if it was not intentional or to document the change if it was.

Connect item: RECONFIGURE WITH OVERRIDE allows disabling of containment when contained databases exist

The above Connect item includes codes to reproduce the behavior. You may have to click on “Expand Details” to see it. Check it out for yourself.