|
Hello all,
I haven't been using profiler for a terribly long time, and I've come across
something that I just can't figure out. I'm running MS Virtual PC to run a
Win2K Server OS with SQL Server 2000 (sp3 i think). Whenever I start up SQL
Profiler - even immediately after a bootup, if I try to pause, stop, or exit
out of profiler, it hangs. The strange part is that it seems to keep on
tracing even though it won't respond anymore. I basically have to end the
process to get out of the profiler window.
Since this is the first time I've seen this before and it is also the first
time that I've used Virtual PC, I have a feeling that the two are related.
So I guess what I'm trying to figure out is what exactly does profiler need
to run properly so that I can check all of my Virtual OS settings. Right
now I have allocated about 650 MB of RAM and I set the Virtual Memory (in
the Virtual machine no less :) to around 800MB I believe. Other
applications are definately not hogging memory either since this happens as
soon as I boot up too..
In addition, I have setup another brand new virtual machine and profiler
works fine. So there is something that I've done with the other non-working
machine since I set it up which has possibly caused the problem.
If anyone has any suggestions for troubleshooting profiler, I would
appreciate them.
Thanks,
Jeff Mair
| 
