跟踪文件 - 如何使用它 [英] Trace file - how to use it

问题描述

我们有一个运行在IIS 6 / ASP.NET 2.0上的应用程序，由SQL Server 2005 STD版本X64支持。有时候，应用程序会与一些愚蠢的消息崩溃（一些文件未找到选择firled1，filed2 ..从mytable）。我从应用程序报告错误时获取了来自sql服务器的活动的跟踪。注意：崩溃只会在该服务器的一些重负载期间遇到，例如几个用户同时创建一些报告。

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.

问题是：如何使用跟踪文件解决的情况？如何检测出错？

The question is: how can I use the trace file to solve the situation? How can I detect what goes wrong?

感谢

推荐答案

在开始使用Profiler时有一个在SQLServerPedia。简而言之，您需要将该跟踪文件导出到表中，然后逐步通过它查看弹出的错误。分析器的跟踪文件或跟踪表本身不会说，这里是你需要修复，以避免此错误任何更多的转储文件将告诉你这里是坏行代码 - 你仍然需要一个经验丰富的DBA来解释结果。您可能希望将跟踪文件带到本地SQL Server用户组会议，并查看是否有人可以帮助您。

I've got a video tutorial on getting started with Profiler at SQLServerPedia. In a nutshell, you'll want to export that trace file into a table, and then step through it in order looking at the errors that popped up. Profiler's trace files or trace tables by themselves won't say, "Here's what you need to fix in order to avoid this error" any more than a dump file will tell you "Here's the bad line of code" - you'll still need an experienced DBA to interpret the results. You may want to take the trace file to your local SQL Server User Group meeting and see if someone can help you.

这篇关于跟踪文件 - 如何使用它的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！