Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

The effect of a set on bandwidth

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • The effect of a set on bandwidth

    Over the past months, I have had some problems with index corruption which required all workstations to be shut down for rebuilding indexes. As a result, I decided to try to minimize the number of indexes. That helped a great deal, but did not eliminate the problem entirely. I then came up with this idea - eliminate the set relationship which I had defined. Instead of a set, I decided to use LQO to create queries on the individual workstations whenever I needed to show 'linked' data. The time required seems minimal and very acceptable. That worked well, but the impact was much more far-reaching that I anticipated. We track daily, weekly and monthly bandwidth usage on all servers. I began to see the real impact of eliminating the set relationship. Additionally, the entire database began to be much more responsive overall..I even eliminated Network Optimization on a whim. The database performance was still very satisfactory.

    I'm not sure what this all means, but I thought it significant enough to post. I have included attachments of the bandwidth monitoring graphs which indicated the bandwidth usage on the Alpha Five server. I instituted the change on a Saturday (a business day for us).

    I'd be interested to hear if others have encountered other solutions/improvements/etc. along these lines.

  • #2
    RE: The effect of a set on bandwidth

    Tom,

    You don't mention your current Alpha version. I can't comment on your bandwidth observationsw, but since converting to 4.5 our index rebuilds are nil. We have, almost, forgotten the problem of disappearing index tags and such problems.
    There can be only one.

    Comment


    • #3
      RE: The effect of a set on bandwidth

      I'm still at 4.03. I wanted to wait until 5.0 to upgrade, and yes, I know 4.5 addresses index corruption. However, the issue became a matter of basic database design when the set was eliminated. I will certainly be trying the set thing once I have 5.0 in my hands.

      Tom Lyon

      Comment


      • #4
        RE: The effect of a set on bandwidth

        Tom,

        As I've stated many times before, the most important resource not to squander is the bandwidth of your network. Any time you apply a filter that does not completely use LQO, it forces A5 to read records to apply the filter expression. This is a big overhead, as you then have to run them all the time (assuming the database is constantly being changed) to refresh them.

        Not using sets is another example of being penny-wise and pound foolish. The speed of access for an A5 set is much lower than building the relationship through another A5 method. The set definition should not have more links than are required for the need. E.g. a report may only need 1 or 2 links, a form may require different links. Create as many sets as the demand requires.

        Index overhead is relatively small, so try to use them. Others may argue that more indexes slow a system down (certainly if you rebuild the indexes), but I have never seen this to be true during regular operation, and if the need is used often enough, is much better than a query.

        Regards,

        Ira J. Perlow
        Computer Systems Design & Associates
        csda@mediaone.net
        Regards,

        Ira J. Perlow
        Computer Systems Design


        CSDA A5 Products
        New - Free CSDA DiagInfo - v1.39, 30 Apr 2013
        CSDA Barcode Functions

        CSDA Code Utility
        CSDA Screen Capture


        Comment


        • #5
          RE: The effect of a set on bandwidth

          Ira said:
          -----------------
          Not using sets is another example of being penny-wise and pound foolish. The speed of access for an A5 set is much lower than building the relationship through another A5 method. The set definition should not have more links than are required for the need. E.g. a report may only need 1 or 2 links, a form may require different links. Create as many sets as the demand requires.
          -----------------

          Yes, I used to think that :) That's why I indicated that I had trimmed the set and indexes down to the bare minimum and simplified as much as I possibly could without affecting operations before trying to operate without a set.

          Still, the database performance without using sets is phenomenal, even taking "The speed of access for an A5 set is much lower than building the relationship through another A5 method" into account.

          That's not to say I understand how to design a database :) I usually use trial and error to determine what will work best based upon my understanding of the software at hand.

          Tom Lyon

          Comment

          Working...
          X