Microsoft Office Tutorials and References
In Depth Information
used to generate usage logs so you can reschedule them. They are already configured
with a default schedule, which works for me.
5. Finally, the last section is for configuring the SQL database information concerning the
logging database. This is where the database server name for the server to hold the
database must be specified (mine has the default RR1 server already in the field), as well as
the database name (again, the default WSS_Logging is fine for me) and how SQL requires
authentication—either Windows authentication, which is what my server uses, or SQL
authentication, which will require username and password credentials. If your server
requires SQL authentication, enter the correct credentials. The default, Windows
authentication, is fine for me.
So for the last three sections, you changed only one setting, and that was to enable health
6. Check all settings on this page to make sure they are correct, and then click OK.
The Processing page will come up, as a database is created, and then you will be dumped
unceremoniously back onto the Monitoring page. If you wait a day, though, there will be usage
data available for the health reports.
Also, to confirm that the data collection has been enabled, you can check the Manage Service
Applications page, as you can see in Figure 3.39 (to get to the page, click Service Applications
Manage Service Applications on the Application Management page).
page with the
Usage and Health
Service applications are available farm-wide, but they are applied per web application (that’s
why they are listed under Application Management and not System Settings). It’s actually the
service application’s proxy that is associated with a web application. Proxies are organized by
two groups, default and custom. Default is the first one and the one with all services available
by, well, default. Custom simply displays all the services, but you can select which ones you