Welcome to MSDN Blogs Sign in | Join | Help

Where is SAC tool?

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.

 

 

FAQ

 

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. 

 

 

 

In contrast to earlier versions of the Maintenance Cleanup task, the SQL Server 2005 version of the task does not automatically delete files in the subdirectories of the specified directory. To delete the files under first-level subfolders, you must explicitly select to do this by checking the Include first-level subfolders option in the Maintenance Cleanup Task dialog box.

Visit the below link for more information

http://msdn2.microsoft.com/en-us/library/ms345177(SQL.90).aspx 

This has been a very common question I have seen in several forums, related to using database mailprofile for SQL Agent jobs, and I thought will post here. If you run into this issue, it could be due to one of the following and I have also have mentioned below how to get around them. Bottom line is datbase mail works fine with SQL Agent jobs and maintenace plans in SP1 on all platforms.

1. If you see this on 64 bit platform and on RTM build, this is a bug that is addressed in SP1.

2. If you see the below error message, it is known issue and this is because of design that requires SQL Agent to restart, if SQL Agent was started before enabling databasemail and setting a new profile. We are evaluating to change this design of not requiring to restart agent for our future release.

Re: 264] An attempt was made to send an email when no email session has been established
This problem will go away after restarting SQL Server Agent in this case

My team keeps emphasizing the importance of community participation and value all the feedback posted in the groups, forums and all possible channels to communicate with you all, the customers; and loop the feedback provided to improve the quality of product. I personally felt the importance after being part of the community during our SP1 release cycle, it really helped to address most of the customer impact defects in our Service Pack1; however, not all could be addressed in the first service pack and we would like to give importance to them and start gathering the impact of those defects. We will evaluate and try to address most of the commonly reported customer bugs in our next Service pack, SP2.

 

This can be done effectively by your active participation in providing feedback. Though there are several ways to do it, the best way to track and evaluate the impact on unaddressed issues across customers, is through reporting them through MSDN product feedback center which is incorporated in SQL Server Management Studio. You can access MSDN Product Feedback Center from Management Studio by selecting “Send Feedback” menu item under “Community” Menu or  by going directly to the below link

http://lab.msdn.microsoft.com/productfeedback/

 

By using this channel, you could log bugs directly or browse over the existing bugs that correspond to the issue you are running into and vote the importance of the fix for that bug. Our team constantly watches the incoming bugs and goes over the importance of the bug to be addressed based on number of voters and the rating of how important the fix is needed.

 

We are starting to plan and work on our next service pack and your input is the key factor for success of SP2!

 

With SQL 2005 released and customers upgrading from SQL2000, it was great to see Newsgroups/Blogs/Forums filled with appreciation feedback on the improvements made in tools. There were concern mails on few areas in the tools domain that lacked some funtionality that used to be in SQL2000. Evey feedback on improvements/issues were evaluated and the most critical ones were addressed in SP1.

 

Below are some of hte important ones addressed in the domain of tools for SP1.

 

SQL Agent

 

Support for controlling the Encryption channel between MSX/TSX

Support MSX/TSX for NetworkService account.

SQL Agent works fine with Databasemail profile on 64 bit platform

XMLA jobsteps over 32k run properly without truncating the command if it were more than 32k

Below noise message logged in SQL Agent log bothering users is now addressed

           "Unable to read local eventlog(the parameter is incorrect) "

 

Maintenance Plans

 

Maintenance Plans cleanup task will support deleting from subdirectories.

Maintenance Plans functionality works with either Tools or SSIS installed on the server box

 

Management Studio

 

Database diagram support objects can now be installed on databases in SQL Server 2000 compatibility mode.

 

SMO

Improved scripting robustness with much more to improve and we are giving high priority

on this for our next release

 

Profiler/Replay:

 

Profiling Analysis Server now shows datetime value in local time and not UTC

 

Management Studio Express

 

New standalone redist shipped as a CTP in November and releasing in final form with SP1.

Included in new Express skus (Express Advanced and Express Toolkit).

Scaled-down subset of SSMS functionality

 

Management Studio Express now has integrated help.

Installing Books Online no longer prevents Management Studio Express from starting.

The effective permissions dialog can now be shown in Management Studio Express.

 

Thanks for all your feedback and we hear and value every feedback we get!

I am Gops Dwarak, member of SQL Server Tools team.

 

"Blog....I should create one', this thought has been for a while and here it is finally. Nearing 5 years of completion with Microsoft what more to say, it has been great pleasure to work for THE software giant.

 

Day one, when I joined Microsoft, it was M1(Milestone 1) of the product, SQL Server 2005. I never knew then, that it will take 5 long years to release it, but the long journey was meaningful and to be part of it was such a great experience and to be really proud of.

 

For the SQL2005 release, I worked on SQL CM and SQL Server Agent (My favorite feature) and venturing into more areas for the next release. The new areas that I will be focusing on will include SQL Mail, DBMail, SQL CMD and Maintenance plans inclusive of SQL Sever Agent. I am ramping up to know more about these features and will be glad to hear of any improvements in the domain of tools, that will drastically help you, the customers. 

 

I am eagerly looking forward to work on the new areas and be part of the next release.

 

About by personal life…

 

I am happily married to Surekha; it will be 3 full years this May 22nd.  My sweet wife takes most of my time, which is left over after work and cricket. I hope she is not reading this. I like to spend my weekends playing cricket provided Surekha permits J

 
Page view tracker