title: Trace file - how to use it
body: <p>we have an application running on an IIS 6/ASP.NET 2.0 backed by a SQL Server 2005 STD edition X64. From time to time, the application crashes with some silly messages (some of the fileds are not found into a "select firled1, filed2.. from mytable"). I obtained a trace of the activity from the sql server taken while the application reported the errors. Note: the crash is encountered only during some heavy load on that server, like creating some reports simmultaneously by several users.</p>
  
  <p>The question is: how can I use the trace file to solve the situation? How can I detect what goes wrong?</p>
  
  <p>Thanks</p>