I tried three times unsuccesfully to alter the DBID values in the trace file by exporting from Profiler to a SQL table, updating, and re-importing the table to Profiler as trace data. Profiler refused to Replay it, but I forgot what it complained about. However, I found it easy to renumber the DBID values of the target databases in my sandbox by DETACHing and reATTACHing them. This made it possible to replay my production trace in the sandbox.
I have not found a credible explanation of the "hit ratio" report. I've seen a guess that it is about cache hit ratios, but I doubt it. ,I tried three times unsuccesfully to alter the DBID values in the trace file by exporting from Profiler to a SQL table, updating, and re-importing the table to Profiler as trace data. Profiler refused to Replay it, but I forgot what it complained about. However, I found it easy to renumber the DBID values of the target databases in my sandbox by DETACHing and reATTACHing them. This made it possible to replay my production trace in the sandbox.
I have not found a credible explanation of the "hit ratio" report. I've seen a guess that it is about cache hit ratios, but I doubt it.
↧