November 2008
Intermediate to advanced
910 pages
27h 16m
English
book
Professional Microsoft® SQL Server® 2008 Administration
by Brian Knight, Ketan Patel, Wayne Snyder, Ross LoForte, Steven Wort
Content preview from Professional Microsoft® SQL Server® 2008 Administration
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
13.7. Monitoring Logs
Another aspect of monitoring that is frequently overlooked is monitoring the various log files available. SQL Server writes its own error log, and then there are the Windows Event logs, and you may find events logged in the Application, Security, or System Event logs.
Traditionally, the SQL Server and Windows Event logs have been viewed separately. The SQL Server Management Studio Log File viewer enables you to combine both sets of logs into a combined view.
For SQL Server 2008, the Log File viewer has been revised and now includes a hierarchical view of events where appropriate.
13.7.1. Monitoring the SQL Server Error Log
The SQL Server Error log can contain a lot of very useful information. It is definitely the place to go looking for deadlock information once the relevant deadlock trace flags have been enabled.
Anytime a significant event issue occurs, the first place to search for additional information should be the SQL Server Error Log.
13.7.2. Monitoring the Windows Event Logs
Three Windows event logs may hold entries of relevance to a SQL Server event:
Application event log
Security event log
System event log
These event logs should be another place that you go to look for information about any issues that arise with SQL Server.
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.