One other thing....the trace started at 10:00 and then again at 12:30 showed results that did not indicated the database was the issue causing the sluggish response. However, the response time was still slow for reports and applications using this server databases. Upon further review, we found a report was started at 9:30 - before the first trace was started - and did not finish for several hours - or after 5:00 pm - also after the traces had completed and we started looking elsewhere.
The question is can a trace pick up this kind of extended activity and what events should be selected to view this type of server usage?