Profiler Problem across RDP

  • 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

  • I seen this a few times on the VM servers we have. In most cases it was I think network issue; the SQL Server profiler was collecting a lot of information when when I pressed "Pause" it took a while for server to realize that trace is to be based and no more information should to be caught by profiler. But in my case most of those were no more then few seconds; I do get good chuck of records back after pressing pause those. I think its normal, haven't dung any deeper into it.

    [font="Arial"]---

    Mohit K. Gupta, MCITP: Database Administrator (2005), My Blog, Twitter: @SQLCAN[/url].
    Microsoft FTE - SQL Server PFE

    * Some time its the search that counts, not the finding...
    * I didn't think so, but if I was wrong, I was wrong. I'd rather do something, and make a mistake than be frightened and be doing nothing. :smooooth:[/font]

    How to ask for help .. Read Best Practices here[/url].

  • Thanks, it is such an odd thing that we just wanted to see if there was anyone out there seeing the same thing.

    For us it does not recover, it can sit for an hour and still be in the same condition.

  • Hmm can't say i have it hang. The management studio has hang on me sometime but it ususally recoveres. Are you logging the trace data to a table directly by any chance?

    Mohit.

    [font="Arial"]---

    Mohit K. Gupta, MCITP: Database Administrator (2005), My Blog, Twitter: @SQLCAN[/url].
    Microsoft FTE - SQL Server PFE

    * Some time its the search that counts, not the finding...
    * I didn't think so, but if I was wrong, I was wrong. I'd rather do something, and make a mistake than be frightened and be doing nothing. :smooooth:[/font]

    How to ask for help .. Read Best Practices here[/url].

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply