General Discussion & Announcements

 View Only

  • 1.  Issues with Server Storage and RocketSoftware Version 6.2 – Any Advice?

    Posted 13 days ago

    Hello everyone,

    I've been facing some challenges with server storage while using RocketSoftware Version 6.2. The main issue is related to inconsistent server storage performance, including slower data access times and occasional errors during high-demand periods.

    Here's the setup:

    • Server Environment: Adequate storage capacity with RAID configuration.

    • Software: RocketSoftware Version 6.2.

    • Issue: Performance inconsistencies and occasional data handling errors.

    Steps taken so far:

    1. Optimized server storage configurations, including drive defragmentation and increasing storage allocation.

    2. Checked for firmware and software updates for both the server and RocketSoftware Version 6.2.

    3. Reviewed server logs for storage-related bottlenecks but couldn't pinpoint a specific issue.

    If anyone has dealt with similar problems involving server storage and RocketSoftware Version 6.2, I'd appreciate your advice. Suggestions for optimizing server storage configurations, resolving performance inconsistencies, or ensuring compatibility would be incredibly helpful.

    Looking forward to your insights. 

    Thank you!



    ------------------------------
    Olivia Barn
    Content Writer
    Rocket Forum Shared Account
    ------------------------------


  • 2.  RE: Issues with Server Storage and RocketSoftware Version 6.2 – Any Advice?

    Posted 10 days ago

    Hi Olivia,

    Are you sure you have identified the product correctly?  I only know about Rocket Software's D3 database and version 6.2 of this database is very, very old. There are other databases provided by Rocket such as Unidata and Universe with different version number sequences. These databases are multivalue databases. Multivalue databases usually use hashed tables referred to as files. If a hash table becomes undersized you can get a lot of overflow chaining. In my experience with the D3 database system performance degrades dramatically when the ratio of total frames used to the original number of frames assigned is greater than 2.  Performance degrades exponentially the bigger this ratio gets. With the D3 database in order to correct this situation you either have to resize the offending file or archive data from it. My apologies if there is a Rocket Software 6.2 product I am not aware of and my comments are of no help to you.



    ------------------------------
    James Carthew
    Application Specialist
    LRS Health Pty Ltd
    Heidelberg VIC AU
    ------------------------------

    Original Message