March 5, 2009 at 8:36 am
When have multiple servers, both physical and virtual. With MS SQL 2k and 2K5. When trouble shooting we use RDP to the server, no problem. Sometimes we get some goofy stuff when running Profiler locally on the server across the remote connection.
On some servers if you hit the pause button, profiler hangs. This is, the Start/Pause/Stop buttons all gray out and in the status bar on the bottom "Pausing Trace", but the trace still runs. At that point you can not do anything because everything is grayed out.
This happen for both 2k and 2k5. We have narrowed it down to only happening on our Virtual server running on VMWare.
Has anyone seen this before? Or have any Ideas? Is it permissions, a setting on VMWare, an setup on the server?
Any ideas or help would help!
Thanks
March 6, 2009 at 7:44 am
I have never personally seen this before, but as a possible work around you may consider running server side traces outside of profiler. You can always create a simple one by going into Profiler and getting the settings the way you want to and then selecting script trace.
At least by doing this you do not have to worry about the Profiler GUI messing up. Obviously it is not always as convenient as just clicking profiler but it is still a workable solution (and one that I prefer in most cases).
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply