I'm getting strange results when I try to analyze data from SQL Server Profiler in SQL Server 2005. It seems like the value for duration is 1000 times more than what it should be.What's behind this anomaly? Late in the SQL Server 2005 development cycle, Microsoft changed the way SQL Server Profiler captures the duration value from milliseconds to microseconds. Surprisingly, the time value for the CPU is still captured in milliseconds. The Profiler GUI automatically...