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

How is performance App. created using alpha five v10.5 handle many records in mysql?

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

    How is performance App. created using alpha five v10.5 handle many records in mysql?

    Hi,

    i am using alpha five version 10.5 to build web based application and have no problem with the performance, but right now i am trying to find a tool to build window based application.

    could someone share about using mysql on desktop application made by alpha five version 10.5? how about the speed if we have many record on a table? i need advise because i am choosing a tool to build a window application for a company that will have many record on the sales data (will be 100000 record for one day for one sales table)? could alpha handle this such data (i will prefer using mysql rather than DBF)?

    Thanks,
    Andi

    #2
    Re: How is performance App. created using alpha five v10.5 handle many records in mys

    That's a lot of records -- 100,000 for one day's work. I have some tables with several hundred thousand records and individual tables that are as large as 31 GB (storing PDF files). I use MySQL for storage for the large tables and dbf files for smaller tables. You're not going to have a performance issue with MySQL tables. You'll have to be careful about setting up your indexes in MySQL, though, since you'll be accumulating one million new records every two weeks.

    Comment


      #3
      Re: How is performance App. created using alpha five v10.5 handle many records in mys

      Hi Peter,

      are you using active link for your mysql table that store PDF and using browse from alpha?

      Comment


        #4
        Re: How is performance App. created using alpha five v10.5 handle many records in mys

        I read that as, "One of the tables might be 100,000 records some day in the future."

        If that's the actual meaning, 100,000 records should be no problem as a DBF file or in MySQL. One of my customers has well over 300,000 records in one desktop DBF table and when asked if things were getting slow and did they want to archive some old records their answer was a firm NO. They said they were having no speed issues. And, after running the application remotely to test other things, I can confirm that as being true.

        The largest web DBF table I current have is just under 50,000 records and there is no noticeable delay or problems with that either.

        Comment


          #5
          Re: How is performance App. created using alpha five v10.5 handle many records in mys

          Cal,
          Your reading of it is more reasonable than mine!
          I have several dbf table with about 300,000 records, and they work just fine. The main reasons I have gone to MySQL records for some tables are (1) security (2) size (dbf tables are limited to, I forget, either 2 or 4 GB, and (3) to take advantage of automatic replication in MySQL (replication beats making a copy of 50 GB of tables). The dbf tables all are rather small even though they have lots of records (largest is about 50 Mb).

          I use Xdialogs and direct SQL calls with AlphaDAO to interact with the MySQL tables, not active link tables.

          - Peter

          Comment


            #6
            Re: How is performance App. created using alpha five v10.5 handle many records in mys

            Peter, I'd be very interested to know why you chose not to use active link tables. My interest is purely for "future edification" - to help me decide what to do when I finally do it - as I haven't really done anything yet with MySQL (or any other SQL db) other than play with it a bit.

            Comment


              #7
              Re: How is performance App. created using alpha five v10.5 handle many records in mys

              Hi Cal.
              I started with MySQL in v.9 and had performance issues with active link tables. Since I usually use Xdialogs in preference to forms for almost all my work, it's not much different to write SQL code than it is to write Xbasic file-handling code.

              e.g. writing
              dim lname as c="Locklin"
              query.filter="last_name="+quote(lname)
              query.order="account"
              dim t as p=table.open("patient")
              t.query_create()
              birthday=t.dob
              address_1=t.address1
              address_2=t.address2

              dim t2 as p=table.open("billing")
              t2.enter_begin()
              t2.account=t.account
              t2.date=date()
              t2.enter_end()
              t.close()


              isn't particularly shorter than
              dim cn as sql::connection
              cn.open("::name::wms")
              dim args as sql::arguments

              sql="SELECT * FROM patient WHERE last_name=:lname ORDER BY account"
              args.set("lname","Locklin")
              cn.execute(sql,args)
              rs=cn.resultSet
              birthday=rs.data("dob")
              address_1=rs.data("address1")
              address_2=rs.data("address2")
              sql="INSERT INTO billing (account,date) VALUES (:account,curdate())"
              args.clear()
              args.set("account",rs.data("account"))
              cn.execute(sql,args)

              In fact, there are even shorter ways to get data from a SQL table, using the sql_lookup() function, for example. And with SQL tables you never have to open or close a table, you just read or write from one.

              Comment


                #8
                Re: How is performance App. created using alpha five v10.5 handle many records in mys

                Hi Peter,

                you write that "I started with MySQL in v.9 and had performance issues with active link tables", i have a few question regarding this to you since i know that you use MySQL:

                1. how about performance active link table in v.10.5 to handle a lot of records? have you tested it?
                2. if you use dialog, do you use browse object or you code manually to show the data as you wrote in your xbasic book?

                regards,
                Andy

                Comment


                  #9
                  Re: How is performance App. created using alpha five v10.5 handle many records in mys

                  Active link tables are supposed to work faster in 10.5; I haven't tested it. I don't use browses or forms in interacting with active link tables, only xdialogs; <i>however</i>, and it's a big however, now that in 10.5 it's possible to put a grid into an xdialog or a form, that should make interacting with SQL tables much simpler! You don't need to write any SQL statements to use a grid to show or update the data in a SQL table, and you don't need to use any active link tables, either.
                  I use passive link tables from time to time for reporting purposes when the report mixes data from SQL tables and dbf tables.

                  Comment

                  Working...
                  X