Clicking on the "Configuration for Features" option brings up a wider assortment of areas toconfigure. Within the dialog you can enable or disable such SQL Server features as CLR integration, XML Web services endpoints and the DAC (dedicated administrator connection).
Figure 4: Configuration for Features
The more important of these options are:
CLR Integration: Modifying this option will allow you to enable or disable SQLCLR routines for the entire SQL Server instance. If you're not quite sure whether you trust thisfeature, this is the place to go to make sure no one can exploit it.
DAC: The dedicated administrator connection is a special connection that can be used byDBAs in case of extreme server resource depletion. Even in cases when other users cannotconnect because there aren't enough resources, SQL Server will attempt to free resourcesfor the DAC. Use this option to enable or disable the DAC for remote access.
OLE Automation: Many SQL Server developers have had to implement workarounds for the lack of features, such as regular expressions in SQL Server. The easiest way to do so inthe past was to use the sp_OA* stored procedures. However, with the introduction of CLR integration, these stored procedures are no longer necessary. If you still need them for backward compatibility, you can re-enable them here.
xp_cmdshell: Much like the OLE automation stored procedures, xp_cmdshell provided agreat workaround for SQL Server limitations in previous versions. However, it's really notrecommended for use in production systems because of security implications when openinga command shell. If you need this for legacy purposes, this is the place to re-enable it.Many of these features are disabled by default because they pose a possible security threat andhave been replaced with better, more secure alternatives. Before re-enabling them, make sure youneed the functionality and try to plan for deprecation as soon as possible. Once your applicationsare updated, return to the tool to disable any unneeded options.