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

Problem performance: Grid Component load > 200 000 record in 20min ? How to solve ??

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

    Problem performance: Grid Component load > 200 000 record in 20min ? How to solve ??

    Hi all !

    I am using a SQL statement as a recordset for a grid. Everything works fine except for navigating the resultset. I don�t know and cannot find any documentation on how the e.object for the onSQLSelectQuery should be set. Can anyone please assist with coding e.recordcount, e.targetpage, e.targetlogicalrecord, e.rowcount and e.pagecount. How to handle pagination in onSQLSelectQuery ??????

    Problem: i have a > 200 000 record data, each load time more waiting (>15 min), so i'm paging BUT I'm not known set parameters (e.recordcount, e.targetpage, e.targetlogicalrecord, e.rowcount and e.pagecount) ?????
    anyone have a better solution or had found a similar solution , please help me!!!!!

    Untitled.png


    Thanks!!!

    #2
    Re: Problem performance: Grid Component load > 200 000 record in 20min ? How to solv

    Hi. Are you saying that when you set up your basic grid (with your query defined as normal and not using any of the server-side events AT ALL) that you have huge delays?
    Because, with standard pagination the grid should only be retrieving the data needed to display the current page. In theory, there "should" be no delays once you let the grid act as it was designed.
    Try creating a new "vanilla" grid using all default values with your basic query in the Query area and showing some fields. This will work like lightning once you don't have database engine issues.

    Comment


      #3
      Re: Stored Procedure - no fields to select

      Originally posted by tranminhthien
      Hi all !

      I am using a SQL statement as a recordset for a grid. Everything works fine except for navigating the resultset. I don’t know and cannot find any documentation on how the e.object for the onSQLSelectQuery should be set. Can anyone please assist with coding e.recordcount, e.targetpage, e.targetlogicalrecord, e.rowcount and e.pagecount. How to handle pagination in onSQLSelectQuery ??????

      Problem: i have a > 200 000 record data, each load time more waiting (>15 min), so i'm paging BUT I'm not known set parameters (e.recordcount, e.targetpage, e.targetlogicalrecord, e.rowcount and e.pagecount) ?????
      anyone have a better solution or had found a similar solution , please help me!!!!!

      [ATTACH=CONFIG]33303[/ATTACH]


      Thanks!!!
      If you are basing a grid on a stored procedure and handling the pagination yourself, then you are responsible for everything. 'everything' includes:

      1. executing a query (presumably a stored procedure that returns a resultset) and returning an result to the Grid
      2. telling the grid how many records are in your query (by setting the e.recordCount parameter (your will need to have a stored procedure that returns the record count)

      If you are handling the pagination yourself, then the result set that you pass to the Grid will already be positioned on the first record you want to display in the grid.
      you must therefore also tell the grid what

      a) physical page of record you are on (e.targetPage). for example, does the resultset you returned represent the 3rd 'page' of record?
      b) the targetLogicalRecord (think targetLogicalRecordNUMBER). -- for example, if the first record in the resultset you returned is the the 2nd page of records, and if there are 10 records per page, the targetLogicalRecord of the first record in the resultset is 11. (this value is used to compute the <LogicalRecordNumber> field (e.targetLogicalRecord)
      c) the number of rows per page in the grid (e.rowCount)
      d) the number of pages in the grid. for example, if the rowCount is 10 and you tell the grid that there are 14 records in your query, then this number will be 2.

      All of this information is documented in the function prototype.

      Comment


        #4
        Re: Problem performance: Grid Component load &gt; 200 000 record in 20min ? How to solv

        Hi! Main problem here! Using Mysql, I have 3 tables, each table have > 200 000 records, and join to each others. If I'm create a Grid Component to be show all records of 3 table(basic query in Properties Query), will take considerable time(20min). So, how to solve ??
        1) Customize paging yourself: set parameters: next, preview, First, and End on Grid Component following yourself. So how to solve....
        2) back-up data, reduce the number of records (not feasible).
        3) ....

        anyone have better solutions. problem: performance load database on alpha five.

        Please help me!
        Thanks!

        Comment


          #5
          Re: Problem performance: Grid Component load &gt; 200 000 record in 20min ? How to solv

          You're going about this the hard way, and there's no need to do all this.

          1. Please do not post the same question/issue multiple times as you did this.

          2. Selwyn Rabins has already responded to you in another of your multiple postings on this - you should pay attention to his response.

          3. Why are you going about it this way? Why not just use Alpha's standard tools to achieve what you need, as I think has already been suggested. If you insist on doing things in the hardest way possible when there are other simple tools available and ignoring advice already given, you're going to quickly run out of people who are willing to spend time helping you.
          -Steve
          sigpic

          Comment


            #6
            Re: Stored Procedure - no fields to select

            Hi! I known but I have no way to solve: performance load database!

            Main problem here!
            I Using Mysql, I have 3 tables, each table have > 200 000 records, and join to each others. If I'm create a Grid Component to be show all records of 3 table(basic query in Properties Query), will take considerable time(>20min). So, how to solve ??

            1) Customize paging yourself: set parameters: next, preview, First, and End on Grid Component following yourself. So how to solve....??. I think alpha five will load all the results to a time before paging, it will more affect performance instead paging from the database query.
            Example: "select * from tbl_a, tbl_b, tbl_c where tbl_a.ID = tbl_b.IDa and tbl_b = tbl_c.IDb"
            "select * from tbl_a, tbl_b, tbl_c where tbl_a.ID = tbl_b.IDa and tbl_b = tbl_c.IDb LIMIT :offset,10", So, how to solve paging here??
            2) back-up data, reduce the number of records (not feasible).
            3) ....

            anyone have better solutions. "performance load database" ????

            Please help me!
            Thanks!

            Comment


              #7
              Re: Problem performance: Grid Component load &gt; 200 000 record in 20min ? How to solv

              So your best approach is to create a union query within the database environment and use that view in A5.
              Or, you can also create a union query directly in A5 (query builder). Your choice. I prefer keeping complex joins within the database environment, but that is a personal preference only.
              There is no need to bother with manual pagination here - let the grid work as it was designed to and you will be very satisfied.
              Note also that the number of records in your tables is not an issue here - an A5 grid will (more or less) only retrieve what is needed for one page at a time.

              Comment

              Working...
              X