Navigation

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search

    ProTop 3.3s has arrived!

    Announcements
    ccc
    2
    4
    2881
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • tom
      tom administrators last edited by

      After a long gestation ProTop 3.3s has arrived!

      Highlights include (but are by no means limited to):

      • Tips and Tricks on the splash screen
      • A startup warning if you do not have -tablerangesize and -indexrangesize set adequately
      • A new screen to show the *rangesize calculations (press "1")
      • Alternate Buffer Pool indicator columns on table and index activity
      • A new "2" data collector to show buffer statistics (some of which are only available in OE 11.7+)
      • New "user experience" metrics - this metric reads a fixed number of records and times it
      • Modified the startup handling of .pf files to increase flexibility
      • Modified UIO to show the current number of locks held per session rather than lock requests/sec (11.7+)
      • Generally took advantage of OE 11.7 improvements where available
      • Added the option to toggle the client statement cache on/off for a session when selecting a session via # or P
      • Added an experimental "task scheduler"

      ... and lots of other stuff!

      1 Reply Last reply Reply Quote 1
      • jdpjamesp
        jdpjamesp last edited by

        Great news Tom. Thanks for the heads up. Does it include the fix for the Windows Bug I keep encountering? If so, I'll make sure to upgrade those installs.

        1 Reply Last reply Reply Quote 0
        • tom
          tom administrators last edited by

          The CreateProcessA fiasco? That is fixed.

          1. Jumped through hoops to support 32 bit _progres executables if you
            happen to be running 32 bit db servers on Windows post 11.3. Which is
            a ridiculous thing to be doing if anyone wants my opinion...

          Which is related to:

          http://knowledgebase.progress.com/articles/Article/Windows-API-call-fails-with-error-13712-in-11-7-64-bit

          (Just in case anyone is wondering why I might not like supporting Windows.)

          jdpjamesp 1 Reply Last reply Reply Quote 0
          • jdpjamesp
            jdpjamesp @tom last edited by

            @tom Yes that's the one. Thanks Tom. Will do the upgrade.

            1 Reply Last reply Reply Quote 0
            • First post
              Last post