Home Dashboard Directory Help

sp_configure - "allow updates" should be an advanced option by Vachhrajani, Nakul


 as Won't Fix Help for as Won't Fix

Sign in
to vote
Type: Suggestion
ID: 662305
Opened: 4/16/2011 8:08:52 AM
Access Restriction: Public


Starting Microsoft SQL Server 2005, direct updates to system tables is not supported/allowed. However, the switch for the same remains in public view.

On a clean install of Microsoft SQL Server, running "sp_configure", shows us the "allow updates" option at the very top - which should not be the case if this setting has no effect, except changing the behaviour of the RECONFIGURE command (per BOL).
Sign in to post a comment.
Posted by Microsoft on 8/1/2011 at 1:14 PM
Thanks for your time in sending us feedback.

The BOL http://msdn.microsoft.com/en-us/library/ms179262.aspx has the “Feature Deprecation” message on the "allow updates" option.
Since SQL Server 2011 (Denali) is the last release to support the feature and the feature will be removed from next version of Microsoft SQL server, we have decided not to make changes on its behavior.

Jason Cho (hyukjec@microsoft.com)
Posted by Microsoft on 5/24/2011 at 12:57 PM
Thanks for your recommendation. We are actively considering it and will try to address it in next major release given time.

Best regards
Microsoft SQL Server Engine Team
Sign in to post a workaround.
Posted by Vachhrajani, Nakul on 4/16/2011 at 8:11 AM
There is no workaround as such because the issue is about the visibility of a configuration option. However, if the "allow updates" switch is enabled, RECONFIGURE will fail and RECONFIGURE WITH OVERRIDE needs to be used (Refer my post - http://beyondrelational.com/blogs/nakul/archive/2011/02/14/ad-hoc-update-to-system-catalogs-is-not-supported-when-using-reconfigure.aspx)