Skip to main content

Acu4gl for sql

  • October 21, 2019
  • 1 reply
  • 0 views
A
  • Anonymous

I have a speed problem with SQL

I try many configuration variable to speed up SQL searching a way to have the same speed with vision

A_MSSQL_ROWCOUNT 10
#A_MSSQL_USE_DROPDOWN_QUERIES TRUE
#A_MSSQL_LIMIT_DROPDOWN ALL
A_MSSQL_NO_RECORD_LOCKS YES
#A_MSSQL_CURSOR_OPTION_1 SCROLL
#A_MSSQL_SELECT_KEY_ONLY yes

#A_MSSQL_FAST_ACCESS 10

    1 reply

    Stephen Hjerpe
    • Stephen Hjerpe
    • Participating Frequently
    • October 22, 2019

    I have a speed problem with SQL

    I try many configuration variable to speed up SQL searching a way to have the same speed with vision

    A_MSSQL_ROWCOUNT 10
    #A_MSSQL_USE_DROPDOWN_QUERIES TRUE
    #A_MSSQL_LIMIT_DROPDOWN ALL
    A_MSSQL_NO_RECORD_LOCKS YES
    #A_MSSQL_CURSOR_OPTION_1 SCROLL
    #A_MSSQL_SELECT_KEY_ONLY yes

    #A_MSSQL_FAST_ACCESS 10

    There's really not enough information in order to assist. Are you basing the performance while attempting one file using myfile_host MSSQL, or are you using default_host MSSQL so that all files go to the database. Most "report" type of data is probably best in Vision, that way you can target data that you want like Accounting or Customer Info in the Database.

    Doing just an Open using Acu4GL MSSQL will take longer than an Open with Vision. Databases provide an additional layer of software the runtime needs to navigate through to get records. There have a number of wikis written about Acu4GL performance, It really depends on what your file IO is doing...

    /cobol/acucobol/w/wikiid-122/23925/acu4gl-for-mssql-performance-problem

    Also, The WHERE constraint can be helpful:

    https://www.microfocus.com/documentation/extend-acucobol/1020/extend-Interoperability-Suite/BKGLGLPERFGL912.html

    Recent badge winners

    Explore all badges
    Terms & ConditionsAccessibility statement