Monthly Archives: August 2010

Configure Database Mail in SQL server 2008

Database Mail

First setup database mail with a profile named SQLAlerts. The profile can be named anything but in these instructions, the profile name SQLAlerts is referenced. If you wish to use a different profile name just substitute accordingly. For procedures in setting up database mail

Define Operator

Connect to the instance using Microsoft SQL Management Studio

Double Click SQL Server Agent

Right Click on Operators and select New Operator



Specify an operator Name, E-mail name, and click OK


Setup SQL Agent Settings

Right Click SQL Server Agent > select Properties


Select Alert System in the left pane

  • Checkmark > Enable mail profile
  • Verify Mail system: Database Mail
  • Verify Mail Profile: SQLAlerts
  • Checkmark > Include body of e-mail in the notification message
  • Click OK.


Restart SQL Agent to activate settings.

Warning: Restarting SQL Agent will cancel any executing jobs.


Define Alert

This sample alert will send an email when TEMPDB database gets larger than 0 KB. This setting is set zero so the alert can be tested. Once verified, you will need to update its settings to a reasonable amount or disable it.

Right Click Alerts and select New Alert


On the General pane specify

  • Name: TEMPDB Growing
  • Type: SQL Server performance condition alert
  • Object: SQLServer:Databases
  • Counter: Data File(s) (KB)
  • Instance: tempdb
  • Alert if counter: rises above
  • Value: 0


Click Response in left pane

  • Checkmark > Notify operators
  • Checkmark > E-mail for the operator


Click Options in left pane

  • Checkmark > Include alert error text in E-mail
  • Delay between response: 2 minutes

Click OK


Verify Alert is Working

The operator should receive an e-mail if not see the troubleshooting section.

Open the Alert. Click History in the left pane.

The fields are updated when the alert is triggered.


 

 

Thanks

 

Prashant Deshpande

Leave a comment

Filed under Uncategorized

Microsoft Community Clips Tool

 

Capture All Desktop Activities with Community Clips

Community Clip, is released by Microsoft Office Lab. Community Clip is free software by which you can capture all your desktop activities with keystrokes and audio .After installing Community Clip it adds an option in Office ribbon as well as in system tray.Community Clips is product from Office Labs so I think it would work with Microsoft Office. Community Clips can be used in capturing a part of desktop or full window for preparing your demos, or for recording the Bugs reproduction as you want to show the bugs in action or you can use it for narration for adding audio to your PPTs so as to make a video of your PPTs as you explain each slide. There are many uses of it.

How to use Community Clips?

  • Download and install community clips.
  • Launch it from System tray icon or from office ribbon



Start capturing the screen.


When you done with capturing the screen you can save the video or upload video to Soapbox or email to your friend. To upload and for email you need to have windows live or hotmail email account.

Download Community Clip

 

Thanks

Prashant Deshpande

Leave a comment

Filed under Uncategorized

Hello world!

Welcome to WordPress.com. This is your first post. Edit or delete it and start blogging!

1 Comment

Filed under Uncategorized

Page Speed Tool

Dear All,

 

From last few days I was working to find out the issue of one of Web server utilizing 100% CPU by w3wp.exe , I have used following tool to collect some of the issue .

 

Using Page Speed

  1. Running Page Speed
  2. Understanding Page Speed performance scores
  3. Recording activity

Running Page Speed

Page Speed generates its results based on the state of the page at the time you run the tool. To ensure the most accurate results, you should wait until the page finishes loading before running Page Speed. Otherwise, Page Speed may not be able to fully analyze resources that haven’t finished downloading.

Alternatively, enable the Automatically run at onload option to have Page Speed automatically start the analysis after any page is properly loaded.

To profile a page with Page Speed:

  • Start Firefox.
  • Select Tools > Firebug > Open Firebug.
  • In the Firebug window, select the Page Speed tab.
  • Navigate to the web page you want to analyze. Wait until the Done message appears on the browser status bar and the progress bar disappears. For pages with streaming video, which don’t show the Done message, wait until the video begins to play.


  • Click Analyze Performance. When the page is analyzed, Page Speed displays the list of web performance best practices and the page’s score on each one, sorted by importance/priority for this page.


  • Optionally, do any of the following:
    • Expand any of the rules to see specific suggestions for improvement.
    • Click any of the rule names to see documentation about each rule.
    • Click Resources to show a detailed list of resources referenced from this page.

Understanding Page Speed performance scores

For each rule, Page Speed gives specific suggestions for improvement, and gives the page a “score” according to a heuristic that weighs a number of factors. It also gives the page a total performance score. 

Understanding per-rule scores

For each rule, there are two kinds of scores: a numeric score, which is a “grade” out of 100; and a color-coded score (green, yellow, or red). The numeric score is a “raw” score that indicates how the page performed on that rule, using some quantitative measure, such as, for example, the total number of DOM elements, or the number of downloaded files. The color-code score factors in the numeric score and the rule’s weight, which is a composite of the potential impact of the rule (based on our experience), and its difficulty of implementation.

This means that there is not a one-to-one mapping between a numeric score and a color code. For example, a score of 0/100 could be translated into a yellow color code if the weight of the rule is not very high. Therefore, you should always refer to the color-code score as the authoritative one.

Here’s how to interpret the color-code scores:

  • High priority. These suggestions represent the largest potential performance wins for relatively little development effort. You should address these items first.
  • Medium priority. These suggestions may represent smaller wins or much more work to implement. You should address these items next.
  • Working fine or low priority. If suggestions are displayed, as indicated with a + sign, they probably represent minor wins. You should only be concerned with these items after you’ve handled the higher-priority ones.
  • Informational messages only. Either these items don’t apply to this page or there was a problem in running the test.

    Tip: If your results show a large number of informational messages, this is likely because you tried to analyze the page before it was fully loaded. Click Refresh Analysis to rerun the analysis.

Understanding the total score

Page Speed also gives you a total numeric and color-code score. The numeric score is calculated as the total numeric score for the page, divided by the total weight of all rules (excluding rules for which you got a “blue”/informational-only result, which are non-scoring). The color-code score is calculated using a heuristic based on the number of green, yellow, and red results.

Recording activity

The Page Speed Activity panel shows a timeline of all browser activities, including network events and JavaScript processing. You can use the panel to further analyze your pages and correlate Page Speed’s performance analysis results with actual timing data.

Note: The Page Speed Activity feature is incompatible with HTTPWatch. Before using it, make sure to disable HTTPWatch: in Firefox, go to Tools > Add-ons, and from the list of add-ons, click Disable for HTTPWatch.

Note that the Page Speed Activity panel shows browser events for all open browser sessions. Use the procedure below to record activity for a single page.

To record activity for one page:

  1. (Re-)start Firefox and clear all tabs.
  2. Clear the browser’s cache.
  3. To clear all browser activity that could be recorded, go to a blank page by entering about:blank in the address bar.
  4. Select Tools > Firebug > Open Firebug.
  5. In the Firebug window, select the Page Speed Activity tab.


  6. Click Record Activity.
  7. Navigate to the page you want to profile. Events are displayed along the timeline.


  8. At any time, to examine the results, stop the timeline from moving by clicking Stop.

    Tip: You can also use the following keyboard shortcuts to start and stop recording: Ctrl-R on Linux and Mac OS X, Alt-R on Windows. 

    Tip: To see the absolute URL of any resource, hover the mouse over the resource to display a tooltip.

  9. See below for more information about the events displayed.

Collecting complete JavaScript function call information

By default, Page Speed Activity collects shallow call graphs that contain the entry and exit times for the function at the bottom of each call stack. This minimizes the observer effect, improving the accuracy of the timeline.

However, you may want to collect complete call graphs that record every function invocation. The Show Uncalled Functions option allows you to:

  • Get a list of uncalled functions. These are functions that were instantiated (parsed) but not called at the time you stop the recording.
  • Get a list of delayable functions. These are functions that were called by the time you stop the recording, showing the difference between each function’s instantiation time and its first invocation time, ordered from the largest to the smallest difference. 

For example, the following screen shot was taken at 7800 ms, and shows a list of functions that had not been called at that point, as well as the time at which they were parsed:


The following screen shot was also taken at 7800 ms, and shows all the functions that had been called by that point, sorted from the most to least delayable; that is, from the largest to smallest difference between parsing time and first invocation:


To record activity and collect complete call graphs for one page:

  • (Re-)start Firefox and clear all tabs.
  • Clear the browser’s cache.
  • To clear all browser activity that could be recorded, go to a blank page by entering about:blank in the address bar.
  • Select Tools > Firebug > Open Firebug.
  • In the Firebug window, select the Page Speed Activity tab, and click the down arrow to display an options pop-up menu*. 
  • From the pop-up menu, select Full Call Graphs.
  • Click Record Activity.
  • Navigate to the page you want to profile. Events are displayed along the timeline.
  • At any time, do any of the following (which will also stop the recording):
    • To view a window showing the list functions that have not yet been called, click Show Uncalled Functions.
    • To view a window showing the list of functions that have been called but which could be delayed, click Show Delayable Functions.

      Tip: To see the full definition of any function, hover the mouse over the function in the Source column to display a tooltip.

    • To save the entire function call tree to a file in protocol buffer format, click Save (not available on Windows). 

Viewing paint snapshots

Starting in Page Speed 1.3 with Firefox 3.5 and higher, the Activity Panel can also display snapshots of the browser’s progressive rendering of a page. When paint snapshots are enabled, and you record activity, Page Speed highlights in yellow each element in a page as it is rendered by the browser. Elements shown in grey are parts of the page that are not viewable in the current browser window without scrolling. You can use these snapshots to help debug progressive rendering problems, and to optimize rendering of elements on the page.

To record activity and view paint events:

  1. (Re-)start Firefox and clear all tabs.
  2. Clear the browser’s cache.
  3. To clear all browser activity that could be recorded, go to a blank page by entering about:blank in the address bar.
  4. Select Tools > Firebug > Open Firebug.
  5. In the Firebug window, select the Page Speed Activity tab, and click the down arrow to display an options pop-up menu. 
  6. From the pop-up menu, select Paint Snapshots.
  7. Click Record Activity.
  8. Navigate to the page you want to profile. Events are displayed along the timeline. The paint snapshots are displayed in a separate pane in the right side of the window.
  9. At any time, to examine the results, stop the timeline from moving by clicking Stop

 

 

Using Page Speed

  1. Running Page Speed
  2. Understanding Page Speed performance scores
  3. Recording activity

Running Page Speed

Page Speed generates its results based on the state of the page at the time you run the tool. To ensure the most accurate results, you should wait until the page finishes loading before running Page Speed. Otherwise, Page Speed may not be able to fully analyze resources that haven’t finished downloading.

Alternatively, enable the Automatically run at onload option to have Page Speed automatically start the analysis after any page is properly loaded.

To profile a page with Page Speed:

  • Start Firefox.
  • Select Tools > Firebug > Open Firebug.
  • In the Firebug window, select the Page Speed tab.
  • Navigate to the web page you want to analyze. Wait until the Done message appears on the browser status bar and the progress bar disappears. For pages with streaming video, which don’t show the Done message, wait until the video begins to play.


  • Click Analyze Performance. When the page is analyzed, Page Speed displays the list of web performance best practices and the page’s score on each one, sorted by importance/priority for this page.


  • Optionally, do any of the following:
    • Expand any of the rules to see specific suggestions for improvement.
    • Click any of the rule names to see documentation about each rule.
    • Click Resources to show a detailed list of resources referenced from this page.

      .

Understanding Page Speed performance scores

For each rule, Page Speed gives specific suggestions for improvement, and gives the page a “score” according to a heuristic that weighs a number of factors. It also gives the page a total performance score. 

Understanding per-rule scores

For each rule, there are two kinds of scores: a numeric score, which is a “grade” out of 100; and a color-coded score (green, yellow, or red). The numeric score is a “raw” score that indicates how the page performed on that rule, using some quantitative measure, such as, for example, the total number of DOM elements, or the number of downloaded files. The color-code score factors in the numeric score and the rule’s weight, which is a composite of the potential impact of the rule (based on our experience), and its difficulty of implementation.

This means that there is not a one-to-one mapping between a numeric score and a color code. For example, a score of 0/100 could be translated into a yellow color code if the weight of the rule is not very high. Therefore, you should always refer to the color-code score as the authoritative one.

Here’s how to interpret the color-code scores:

  • High priority. These suggestions represent the largest potential performance wins for relatively little development effort. You should address these items first.
  • Medium priority. These suggestions may represent smaller wins or much more work to implement. You should address these items next.
  • Working fine or low priority. If suggestions are displayed, as indicated with a + sign, they probably represent minor wins. You should only be concerned with these items after you’ve handled the higher-priority ones.
  • Informational messages only. Either these items don’t apply to this page or there was a problem in running the test.

    Tip: If your results show a large number of informational messages, this is likely because you tried to analyze the page before it was fully loaded. Click Refresh Analysis to rerun the analysis.

Understanding the total score

Page Speed also gives you a total numeric and color-code score. The numeric score is calculated as the total numeric score for the page, divided by the total weight of all rules (excluding rules for which you got a “blue”/informational-only result, which are non-scoring). The color-code score is calculated using a heuristic based on the number of green, yellow, and red results.

Recording activity

The Page Speed Activity panel shows a timeline of all browser activities, including network events and JavaScript processing. You can use the panel to further analyze your pages and correlate Page Speed’s performance analysis results with actual timing data.

Note: The Page Speed Activity feature is incompatible with HTTPWatch. Before using it, make sure to disable HTTPWatch: in Firefox, go to Tools > Add-ons, and from the list of add-ons, click Disable for HTTPWatch.

Note that the Page Speed Activity panel shows browser events for all open browser sessions. Use the procedure below to record activity for a single page.

To record activity for one page:

  1. (Re-)start Firefox and clear all tabs.
  2. Clear the browser’s cache.
  3. To clear all browser activity that could be recorded, go to a blank page by entering about:blank in the address bar.
  4. Select Tools > Firebug > Open Firebug.
  5. In the Firebug window, select the Page Speed Activity tab.


  6. Click Record Activity.
  7. Navigate to the page you want to profile. Events are displayed along the timeline.


  8. At any time, to examine the results, stop the timeline from moving by clicking Stop.

    Tip: You can also use the following keyboard shortcuts to start and stop recording: Ctrl-R on Linux and Mac OS X, Alt-R on Windows. 

    Tip: To see the absolute URL of any resource, hover the mouse over the resource to display a tooltip.

  9. See below for more information about the events displayed.

Understanding the Page Speed Activity events

The Activity panel shows browser events along a timeline, for each resource required for the page being recorded. Events are represented in time slices of 10 milliseconds. If the browser event doesn’t take the entire 10 milliseconds, the event is shown in a lighter shade. Segments in the timeline in which no colored event is displayed indicate that the browser is occupied with other processing, such as DOM and CSS parsing, Flash ActionScript processing, painting, operating system activities and so on.

Collecting complete JavaScript function call information

By default, Page Speed Activity collects shallow call graphs that contain the entry and exit times for the function at the bottom of each call stack. This minimizes the observer effect, improving the accuracy of the timeline.

However, you may want to collect complete call graphs that record every function invocation. The Show Uncalled Functions option allows you to:

  • Get a list of uncalled functions. These are functions that were instantiated (parsed) but not called at the time you stop the recording.
  • Get a list of delayable functions. These are functions that were called by the time you stop the recording, showing the difference between each function’s instantiation time and its first invocation time, ordered from the largest to the smallest difference. 

For example, the following screen shot was taken at 7800 ms, and shows a list of functions that had not been called at that point, as well as the time at which they were parsed:


The following screen shot was also taken at 7800 ms, and shows all the functions that had been called by that point, sorted from the most to least delayable; that is, from the largest to smallest difference between parsing time and first invocation:


To record activity and collect complete call graphs for one page:

  • (Re-)start Firefox and clear all tabs.
  • Clear the browser’s cache.
  • To clear all browser activity that could be recorded, go to a blank page by entering about:blank in the address bar.
  • Select Tools > Firebug > Open Firebug.
  • In the Firebug window, select the Page Speed Activity tab, and click the down arrow to display an options pop-up menu*. 
  • From the pop-up menu, select Full Call Graphs.
  • Click Record Activity.
  • Navigate to the page you want to profile. Events are displayed along the timeline.
  • At any time, do any of the following (which will also stop the recording):
    • To view a window showing the list functions that have not yet been called, click Show Uncalled Functions.
    • To view a window showing the list of functions that have been called but which could be delayed, click Show Delayable Functions.

      Tip: To see the full definition of any function, hover the mouse over the function in the Source column to display a tooltip.

    • To save the entire function call tree to a file in protocol buffer format, click Save (not available on Windows). 

Viewing paint snapshots

Starting in Page Speed 1.3 with Firefox 3.5 and higher, the Activity Panel can also display snapshots of the browser’s progressive rendering of a page. When paint snapshots are enabled, and you record activity, Page Speed highlights in yellow each element in a page as it is rendered by the browser. Elements shown in grey are parts of the page that are not viewable in the current browser window without scrolling. You can use these snapshots to help debug progressive rendering problems, and to optimize rendering of elements on the page; for tips, see the article Capturing and analyzing browser paint events using Page Speed Activity.

For example, the following screen shot shows the text and icon elements being painted, followed by the form input field, followed by the form buttons:

 

To record activity and view paint events:

  1. (Re-)start Firefox and clear all tabs.
  2. Clear the browser’s cache.
  3. To clear all browser activity that could be recorded, go to a blank page by entering about:blank in the address bar.
  4. Select Tools > Firebug > Open Firebug.
  5. In the Firebug window, select the Page Speed Activity tab, and click the down arrow to display an options pop-up menu. 
  6. From the pop-up menu, select Paint Snapshots.
  7. Click Record Activity.
  8. Navigate to the page you want to profile. Events are displayed along the timeline. The paint snapshots are displayed in a separate pane in the right side of the window.
  9. At any time, to examine the results, stop the timeline from moving by clicking Stop

Thanks

 

Prashant Deshpande

Leave a comment

Filed under Uncategorized

Enable Object Explorer in SQL server 2008 R2

Dear All

Today after installing Microsoft SQL server 2008 R2 on one of developers system , Object Explorer was not getting opened .

To resolve this issue following steps are used and Object explorer got visible

Window —> Reset Window Layout in Management Studio.

 

Thanks

Prashant Deshpande

 

2 Comments

Filed under Uncategorized

Enable Data modification from SQL Management Studio

 

Dear All

SQL server 2008 has given a facility to connect to remote database server by using Management studio 2008, default when we install Management studio it gives read only access to all the databases even to Database Owner due to built in security feature of management studio 2008.

We need to enable the Database table changes option which will allow making changes in database objects.

To enable Data modification from SQL Management Studio 2008, on Client system they need to uncheck the following check box from tools option Designers Table and Database Designers Dialog box.

 

 

 

 

Thanks

 

Prashant Deshpande

Leave a comment

Filed under Uncategorized

Use of Core parking and how to disable it

 

 

Introduction

 

Core Parking, a new feature in Windows Server 2008 R2, is a Windows scheduling technology that improves energy efficiency by dynamically scaling the number of processor cores in use. When cores are not in use, they transition to a state that consumes less power.

In addition to managing cores on a single processor, Core Parking also helps to scale throughput and optimize energy efficiency across multiple processors in a server system. Additionally, on systems with processors equipped with Intel Hyper Threading technology, Core Parking is leveraged to help intelligently schedule work between threads.

Core Parking is enabled by default on all Servers with multi-core processors that run Windows Server 2008 R2. Additionally, core parking is enabled client systems with multi core, hyper threaded processors running Windows 7 client.

 

 


 

1 Resource Monitor

Figure 1 shows a screen capture from a system with two quad core Xeon processors (eight processors) running Windows Server 2008 R2. The Resource Monitor application clearly displays the status of each core. In this instance, six of eight cores are parked. You can also determine if a core is parked or unparked by checking the “Parking Status” counter in the Performance Monitor tool (perfmon.exe). “Parking Status” can be found under the “Processor Information” performance counter group.

 

 

Figure 1. Resource Monitor


 

2 Disabling Core Parking

While Core Parking is beneficial for most customers, there are certain scenarios Core Parking should be disabled in such as in a high performance or high availability environment. Core Parking can be disabled with the following commands:

 

1. Powercfg.exe /L

 

This dumps the list of power schemes. Find the SCHEME_GUID corresponding to the current selected power policy – it is marked with an asterisk to the right.

 

2. Powercfg.exe /QH > current-power-cfg.txt

 

Open the text file and find the SUB_GUID on the line that looks like this: Subgroup GUID: 54533251-82be-4824-96c1-47b60b740d00 (Processor power management)

 

Then find the SETTING_GUID on the line that looks like this: Power Setting GUID: ea062031-0e34-4ff1-9b6d-eb1059334028 (Processor performance core parking max cores)

 

3. To set the wall-powered value, enter:

 

Powercfg.exe -SETACVALUEINDEX <SCHEME_GUID> <SUB_GUID> <SETTING_GUID> 0

4. Restart the Server

 

Its all done J

Thanks

 

Prashant Deshpande

 


 

Leave a comment

Filed under Uncategorized