You are on page 1of 16

To view overall system Performance… Go to Control Panel then Administrator Tools and click over Performance

application.

We can view the system usage and performance graph in three ways, i.e Graph, Histogram and List.

View Graph

View Histogram

View List

Add button

To add the counters to the existing graph just click over the ADD button from the Tool bar. Then it displays the following Add Counter dialogue box. In this box we have different types of options. 1. Performance Object: This box we have different types of Performance object like Memory, Processor, cache, Physical disk, etc.

To change the grid time (Red line moves once per second) click the right button over the Graph and click over Property. Then it displays, Grid Line

Change the Grid line time

In SQL Server to display the Query process that how it is executes. For this go to Query Menu and Click over the Display Estimated Executed Plan (Ctrl + L) command, then it displays Structure of Query execution.

TUNNING USING SQL SERVER BY INDEXES
We can also tune the database using the concept Index. The SQL Server also recommends using the index for some of the Columns. For this the process is, From SQL Server click over the Query Menu and Click Index Tuning Wizard Button, i.e,

Then it displays the following window...

Click over Next and then click on Thorough and click on Next.

Again click next.

From the following window, check the tables which we need to use in the Query. And then click next.

Then it shows the Check box which are to be recommended for the index to be used in the Query.

To view the analysis for the usage memory for the recommended Indexes and other columns just click over the Analysis Command.

It shows the recommended configuration for the Index columns and others.

In these windows we can also see the analysis in different ways. Like to find the size for the each table which is used in the query. Just pop up the Reports combo box… Then Select the Table analysis Repot then it displays the analysis for the different tables which are exist in the current query.

SQL PROFILER
SQL Profiler is a graphical tool that allows system administrators to monitor events in an instance of Microsoft® SQL Server™. You can capture and save data about each event to a file or SQL Server table to analyze later. For example, you can monitor a production environment to see which stored procedures are hampering performances by executing too slowly. Use SQL Profiler to monitor only the events in which you are interested. If traces are becoming too large, you can filter them based on the information you want, so that only a subset of the event data is collected. Monitoring too many events adds overhead to the server and the monitoring process and can cause the trace file or trace table to grow very large, especially when the monitoring process takes place over a long period of time. After you have traced events, SQL Profiler allows captured event data to be replayed against an instance of SQL Server, thereby effectively reexecuting the saved events as they occurred originally. Use SQL Profiler to:
• • • •

Monitor the performance of an instance of SQL Server. Debug Transact-SQL statements and stored procedures. Identify slow-executing queries. Test SQL statements and stored procedures in the development phase of a project by single-stepping through statements to confirm that the code works as expected. Troubleshoot problems in SQL Server by capturing events on a production system and replaying them on a test system. This is useful for testing or debugging purposes and allows users to continue using the production system without interference. Audit and review activity that occurred on an instance of SQL Server. This allows a security administrator to review any of the auditing events, including the success and failure of a login attempt and the success and failure of permissions in accessing statements and objects.

SQL Profiler provides a graphical user interface to a set of stored procedures that can be used to monitor an instance of SQL Server. For example, it is possible to create your own application that uses SQL Profiler stored procedures to monitor SQL Server. You must have at least 10 megabytes (MB) of free space to run SQL Profiler. If free space drops below 10 MB while you are using SQL Profiler, all SQL Profiler functions will stop.

To set these just open the SQL Server Profiler, then click on New Trace and click on Event tab, which contains the different types of events which are displayed in the Event Profiler. In this we can add the different events which we require like, cursors, database, Locks, Objects, Scans, Servers and so son.

In the above windows we can also find a tab filters. In this we can view and also restrict the users with their windows desktop id. With this we can view the performance of a query from the client system. Just by writing the name of the user we can view properties and performance.

Click on the Run button to view the different options with its time taken to execute.