A pristine new environment awaits and will soon provide SharePoint services to your user
base.
Over the next few weeks, users will be added to your new farm. Any shortfalls in the original
design can then be identified and documented as part of design tuning. If there are any
errors or omissions in the design, they can be examined and remedied as part of the rollout
process.
This objective covers how to:
- Establish baseline performance.
- Perform client-side tracing.
- Perform server-side tracing.
- Analyze usage data.
- Enable a Developer Dashboard.
- Analyze diagnostic logs.
Summary:
- A data collector set can be configured to capture performance counters on a regular basis for analysis.
- A data collector set created on one server can be saved as a template and then used on another server in the farm.
- Client-side tracing is available only for BCS.
- Server-site traces for BCS have matching activity IDs, also known as correlation IDs.
- The views in the SharePoint Usage and Health logging database can be analyzed and exported to Excel for further analysis.
- Although the Developer Dashboard has three settings (On, Off, and On Demand), there are effectively only two settings: Off and On Demand.
- The ULS log has six level settings: none, unexpected, monitorable, high, medium, and verbose.
