16.01.2013 Views

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 10: Performance Monitoring in <strong>Microsoft</strong> Office SharePoint Portal Server 2003 265<br />

Windows Server 2003 Event Logs<br />

You can configure the level of information <strong>and</strong> types of events to be logged in Windows<br />

Server 2003 event logs. Check these event logs regularly to verify that the<br />

required operating system, SharePoint Portal Server, <strong>and</strong> IIS are running.<br />

More Info The .NET Framework SDK provides customizable components<br />

for managing logs programmatically. For more information about managing<br />

event logs using these components, see the .NET documentation about<br />

event logs at http://msdn.microsoft.com/vstudio/using/underst<strong>and</strong>/perf<br />

/default.aspx?pull=/library/en-us/dnbda/html/exceptdotnet.asp.<br />

SQL Server 2000 Logs<br />

SQL Server 2000 provides logs to monitor server processes, databases, <strong>and</strong> user<br />

activities. Checking SQL Server logs is the first step in analyzing database-related<br />

problems. After checking logs, you can trace problems by using other tools such as<br />

SQL Server Profiler for detailed analysis <strong>and</strong> resolution of problems.<br />

When you create a new portal, SharePoint Portal Server creates three new databases,<br />

in addition to a configuration database that can be shared among different<br />

portals. When these databases are created, SharePoint Portal Server allocates default<br />

sizes for data files <strong>and</strong> transaction logs. To avoid the additional overhead added by<br />

the auto-grow feature of SQL Server, you can increase the initial size of data <strong>and</strong><br />

transaction files based on your usage prediction. Continually using the auto-grow<br />

feature of data file <strong>and</strong> transaction logs can slow down database-related activities.<br />

IIS 6.0 <strong>and</strong> SharePoint Portal Server Usage Analysis Processing Logs<br />

The IIS <strong>and</strong> SharePoint Portal Server Usage Analysis Processing logs provide extensive<br />

information in log files that can detect how end users access <strong>and</strong> use SharePoint<br />

Portal Server with possible errors. These log files also can be used for peak-usage<br />

analysis <strong>and</strong> to determine which pages are most frequently used. Peak-usage analysis<br />

in conjunction with records obtained from performance monitoring logs can be<br />

used for capacity planning. Based on this information, you can decide if you need<br />

an additional server in the front-end Web server farm.<br />

SharePoint Portal Server Diagnostic Tools<br />

You can configure diagnostic tools through the SharePoint Portal Server Central<br />

Administration interface to detect errors <strong>and</strong> help with troubleshooting. You can<br />

configure these logs to record SharePoint Portal Server–related messages at the following<br />

levels:

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!