Surface Area Configuration (SAC) tool will be removed in SQL 2008 release. This tool exposed two major functionalities.
Surface Area Configuration for Services and Connections
Surface Area Configuration for Features
A. In SQL 2008, starting CTP5 release, the functionality of Surface Area Configuration for Services and Connections can now be performed using SQL CM.
SQL Configuration Manager (SQL CM) will be the GUI tool to (Video to demo this will be here soon.)
Configure Remote access for Database Engine
Stat SQL CM and browse to SQL Server Network Configuration Node and select the SQL Server Instance
The right pane displays protocol list. Right click on TCP/IP protocol and Enable it.
SQL Service requires restart for the changes to be in effect.
and Configure the services - like start/stop/pause/restart/update service accounts.
Stat SQL CM and browse to SQL Server Services and select the SQL Server Instance
The right pane displays the services list. Right click on a particular service and you will have start/stop/pause/restart options
Right click on a service and select properties. “Log On” tab is the place to change service account
B. and the functionality of Surface Area Configuration of Features can be performed using SSMS.
SQL Server Management Studio(SSMS) will be the GUI tool to configure the features.
Method 1 - Configure directly through facet
Launch SSMS and connect to the Server. Right Click on Server and select Policies->Facet. Drop down the Facet combo box and select Surface Area Configuration Facet. One can Enable/Disable a feature from this dialog and click ok.
Method 2 - By Evaluating DMF Policies and Configuring.
Launch SSMS and connect to the Server. Right Click on Server and select Policies->Facet. Drop down the Facet combo box and select Surface Area Configuration Facet. Set the feature status as required. Then select "New Policy from Facet" and you can save it to local server or to a file and evaluate this policy on the server manually. If the policy fails because of unexpected value, one can configure to the policy's expected value by clicking "Configure". Video to demo this will be here soon.
There is one more way to create policy from Facets through SSMS. Launch SSMS and connect to the Server. Go to Management->Policy Management->Policies node and Create policy. Video to demo this will be here soon. This option gives users granular option of selecting the desired features to be evaluated
Starting CTP6, Command line support will be provided through Powershell over
SMO(WMI) API - for configuring services
DMF object model - for configuring features. Video to demo this will be here soon.
1. Can we use DMF Facets to configure features of Analysis and Reporting Server ?
Yes. Using Method 1 and Method 2 as specified above. For Method 2 - the policy needs to be created by connecting to Database Engine Server and can be evaluated from Analysis or Reporting Server by clicking on Server->Policies->Evaluate and selecting the appropriate policy.
2. Can we schedule Analysis or Reporting Server Surface Area Configuration Policies?
No. The only supported execution mode for Analysis and Reporting server policies is "On Demand" - by running manually.
3. Can we monitor changes of Surface Area Configuration for Analysis and Reporting Server ?
No. This is supported only for Database Engine. see # 2
4. Surface Area Configuration through DMF - Does it work against 9.0 and 8.0 Servers as well?
Yes, Surface Area Configuration through DMF works for 9.0 and 8.0 Servers for Database Engine. For Analysis and Reporting Server, it will support against 9.0.
Surface Area Configuration (SAC) tool will be removed in SQL 2008 release. This tool exposed two major
This is great, except for when the service won't start and the configuration can only happen in SSMS...which means you can't configure it, because the service isn't started...and you can only connect to a started service in SSMS, whereas in the SAC tool, the config could be made, no matter if the service was started or not.
Good! Other than SSMS, the SQL tools with 2005 are garbage. At least on the x64 platform. Hopefully Microsoft will support SQL Server 2008 better than they are currently supporting SQL Server 2005.
If you're installing the latest release of SQL Server 2008, you'll probably immediately start looking
The new CM is awesome, love it.