SQL Server Profiler   «Prev  Next»

Lesson 10

SQL Server Profiler Conclusion

In this module, you learned how to use SQL Server Profiler to help identify problems with SQL Server. Now you should be able to:
  1. Identify the key features of SQL Server Profiler
  2. Create a trace
  3. Identify the events that SQL Server Profiler can track
  4. Identify the information that can be traced
  5. Run a trace
  6. Replay a trace
  7. Use the Index Tuning Wizard
  8. Use the Trace Wizard

The following terms were introduced to you in this module:

Glossary Terms

  1. Event:A significant occurrence
  2. Event category:A group of events
  3. Event class:A group of events
  4. Filter:Limits what is viewed
  5. Trace:The information that SQL Server profiler gathers
  6. Index Tuning Wizard:A wizard that helps you develop the correct indexes .for a table
  7. Trace Wizard:A SQL Server wizard that helps you set up a trace

In the next module you will learn how to monitor SQL Sever with various operating system tools.
The "SQL Server Profiler" utility has been deprecated in SQL-Server.
Microsoft has introduced Extended Events as a successor technology to replace SQL Server Profiler ¹ ². Extended Events offers several advantages, including a built-in GUI and potentially better performance. It can audit a wide range of actions, but it suffers from some deficiencies, such as not being able to provide information on what was deleted or inserted. Also, there is no means for before-and-after auditing to compare new and old values for updates.

SQL Server Profiler -Exercise

Click the Exercise link to see how well you have mastered the concepts in this module.
SQL Server Profiler-exercise