Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

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

Corrupted Indexes frequently

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

    Corrupted Indexes frequently

    Hi everyone,

    Our multi-user(80 users) application, builded with Alpha 5 has very, very often corrupted indexes. The big problem is that they occur at any moment so it's verry hard to reproduce a corrupted index in a test enviroment.

    I'd like to know what is really causing these corrupted index.
    By tracking down the cause I can solve the problem.

    Does anyone has a clue? Or does anyone has similar problems?
    And defiantly most important, how to solve/prevent/troubleshoot them.
    Maybe there is sort of tracetool/technique available like mssql server has.

    Thanks in advance,

    Brendo
    Ing./bict Brendo Bongers
    Software Engineer

    http://www.brendobongers.nl

    "There's more than one way to skin a cat."

    #2
    Re: Corrupted Indexes frequently

    Originally posted by B.B.Bongers
    Hi everyone,

    Our multi-user(80 users) application, builded with Alpha 5 has very, very often corrupted indexes. The big problem is that they occur at any moment so it's verry hard to reproduce a corrupted index in a test enviroment.

    I'd like to know what is really causing these corrupted index.
    By tracking down the cause I can solve the problem.

    Does anyone has a clue? Or does anyone has similar problems?
    And defiantly most important, how to solve/prevent/troubleshoot them.
    Maybe there is sort of tracetool/technique available like mssql server has.

    Thanks in advance,

    Brendo
    Frequently discussed, check the similar threads at the bottom of this page or search.
    There can be only one.

    Comment


      #3
      Re: Corrupted Indexes frequently

      Depending upon which operating systems are deployed you might check to verify that opportunistic locking has been disabled on all machines, including especially the machine acting as server.

      Are the problems occuring with "filtered" indexes?
      ... with "unique" indexes?

      -- tom

      Comment


        #4
        Re: Corrupted Indexes frequently

        Originally posted by Stan Mathews
        Frequently discussed, check the similar threads at the bottom of this page or search.
        Thanks Stan, but with more than 240 tables and with a "lot" of users these mentioned suggestions/solutions are too vague.
        There most be a better effective methodology to pinpoint the cause.(like tracing). Where to look, which action did cause it, which table, which set etcetra.
        Ing./bict Brendo Bongers
        Software Engineer

        http://www.brendobongers.nl

        "There's more than one way to skin a cat."

        Comment


          #5
          Re: Corrupted Indexes frequently

          do you have any indexes on numeric fields, and are the fields longer than 10 digits?

          if so, a somewhat interesting tidbit, if you use expressions anywhere as in scripts, if the length of the numeric field is greater than 10, and you want to reference the numeric field as a string, you can't say str(numericfield)

          say the field is 12 digits

          say str(numericfield,12,0) or str(numericfield,12,2)

          otherwise it returns unrecognizable values

          my own experience with "corrupted" indexes is that it always turns out to be a subtle problm with my code and/or especially having given Alpha a filter or query that cannot be resolved which will drop an index. Also, the more users you have the simpler you have to make things - like not using filters in indexes or sets. Better to handle the filtering/ordering directly that via indexes or set definitions.
          Last edited by martinwcole; 08-01-2006, 09:42 PM.
          Cole Custom Programming - Terrell, Texas
          972 524 8714
          [email protected]

          ____________________
          "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

          Comment


            #6
            Re: Corrupted Indexes frequently

            We struggled with index corruptions for a long time and only solved the problem by a series of design changes effected over a period of about a year. We still have index corruptions occasionally but nothing remotely like before the redesign.

            Our application is large with many sites installed but none would ever have reached 80 simultaneous users. Our largest sites currently would be in the range of 20 to 40 concurrent users.

            We were never able to come up with method for tracking down the root cause. There were probably several causes. Our design changes were based on having users leave their screens "as was" when the error occurred and we noted the areas where the errors occurred.

            Not surprisingly the errors occurred most often in those parts of the application where the users spent most of their time. As a result we focused on (1) reducing the number of indexes attached to any one table (and removal of filtered indexes), (2) set design simplification and (3) form redesign that ultimately helped enormously.
            Finian

            Comment


              #7
              Re: Corrupted Indexes frequently

              Thanks for the suggestions so far.
              It will be I time consuming process to look at all tables and sets.
              Maybe Alpha will developed in the future a tool to measure the state of database/extended alpha/dbf files.

              I.e.
              - How often is a particular table queried.
              - Which queries are abnormally slow.
              - Which index is never used?
              - Which key will be a candidate to index?

              Critical business applications can't live without it.
              Last edited by B.B.Bongers; 08-04-2006, 03:20 PM.
              Ing./bict Brendo Bongers
              Software Engineer

              http://www.brendobongers.nl

              "There's more than one way to skin a cat."

              Comment


                #8
                Re: Corrupted Indexes frequently

                Brendo,

                Maybe not what you're asking for but you can do some profiling.

                Code:
                PROFILER_BEGIN()....PROFILER_END()
                Marcel

                I hear and I forget. I see and I remember. I do and I understand.
                ---- Confusius ----

                Comment


                  #9
                  Re: Corrupted Indexes frequently

                  Hi Marcel,

                  We are going to trace users that are reporting open indexes.
                  Maybe we could find some patterns in the tracelog.
                  Ing./bict Brendo Bongers
                  Software Engineer

                  http://www.brendobongers.nl

                  "There's more than one way to skin a cat."

                  Comment

                  Working...
                  X