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



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

Extreme performance penalty using SQL Server connection

  • Filter
  • Time
  • Show
Clear All
new posts

  • Extreme performance penalty using SQL Server connection

    Using SQL Server 2016. The ADO Connection is using Sql 2016 version.
    I set a tabled-value function as data source for a list control. I have an argument ( :FromDate ) fed by a control in the ux, then the to use the table-valued function i use:

    select * from ExpoDetails ( :FromDate )

    Of course to make this work i have to de-select "use portable sql".

    This works, but it takes 25 to 30 seconds to run ( for a 30K records return ) while running the same query in SSMS is almost instant, one second at most.

    Tried selecting 2014,2017,2012 and 2008 in the sql version in the sql connection , with minor effects.

    Is there some way to improve this?


  • #2
    Re: Extreme performance penalty using SQL Server connection

    I selected "paginate data" in the list control, took down the time to 5-6 seconds, which is livable :-)


    • #3
      Re: Extreme performance penalty using SQL Server connection

      How many columns are in ExpoDetails? Do you really need all of them? If not then select the individual columns you need. Also, do you really need all 30,000 records? If not filter it some more. You can also try using a viewbox. It's more lightweight than the list control.
      Mike Brown - Contact Me
      Programmatic Technologies, LLC
      Independent Developer & Consultant


      • #4
        Re: Extreme performance penalty using SQL Server connection

        Well in fact i need to export to Excel, after the list is loaded the user clicks export. In fact i could write code to export directly, but my users like to visualize the results prior to exporting. I generally do this with grids, but calling a table-valued function with an argument in a grid is a pita...
        So, as stated above, i selected the "paginate" option in the grid, and after reducing the first load to 15 records, it loads in around 3 seconds, which is great. Clicking on the "excel export" button runs the query straight from SQL to excel, which indeed takes 1 to 2 seconds, so all is well.


        • #5
          Re: Extreme performance penalty using SQL Server connection

          In sql do you have an index on the field used to filter the records?
          Glen Schild

          My Blog


          • #6
            Re: Extreme performance penalty using SQL Server connection

            Index will speed it up.
            Select from reads the whole Db which is not what you need.
            See our Hybrid Option here;


            • #7
              Re: Extreme performance penalty using SQL Server connection

              It's not an sql issue, as stated, my query takes less than a second to run.
              Without selecting pagination, the list control needed to load 30000 rows, that's why it took so long. I set pagination and selected 15 rows, it takes now 2 to 3 seconds


              • #8
                Re: Extreme performance penalty using SQL Server connection

                try virtualization on the list, so all the data is sent to the client and loaded, but its not all put into the DOM (HTML)