Sage 100

 View Only
  • 1.  v2017 ADV - CSODBC When running an Excel query fr

    Posted 02-07-2018 10:27
    v2017 ADV - CSODBC When running an Excel query from the server, the query runs in a little over 2 minutes. When running from the workstation, 17 + minutes. Not good. Server was rebooted last night (I stopped the ODBC service just in case to clear the memory leak). Ping the server from workstation, response is < 0 MS. I DFDM'd the sy_system file and everything looked fine there in the csodbc section. I changed the server name in the Query path to the IP address. That shaved the query time from 17 down to 12 minutes. I have forwared the AV KB article for excluding file extension to their IT. They say that is set up properly. I am waiting to hear back from IT regarding the PDF's that @BrettZimmerman posted last week. Any other thoughts? Getting this to run properly is not a slam dunk! TIA


  • 2.  RE: v2017 ADV - CSODBC When running an Excel query fr

    Posted 02-07-2018 13:26
    May not be helpful but wondering if the Excel query is taking advantage of CS ODBC. In Excel is the connection for your query using SOTAMAS90 DSN or is it using a connection string? If SOTAMAS90, CS ODBC is used if you've gone to User Maintenance and checked the box for it. It effectively means on the wkstn, the Server tab of SOTAMAS90 DSN in ODBC Admin has Server Name/IP and Port filled in for you after restarting the Launcher at the wkstn once. So then in Excel: * If using SOTAMAS90, if wkstn DSN has Server tab populated, it's using CS ODBC. Otherwise it's not. * If NOT using SOTAMAS90 because you used a connection string instead, you can edit that to take advantage of CS ODBC by adding this to it: RemotePVKIOHost=MYSERVER; RemotePVKIOPort=20222; (Substitute MYSERVER for actual server name or IP)


  • 3.  RE: v2017 ADV - CSODBC When running an Excel query fr

    Posted 02-07-2018 13:50
    User maintenance option for csodbc is selected for that user. Query connection is below. NIC is set at 1 GB speed. Interesting that changing the DSN to the server IP instead of server name sped things by 33%. Still not the same speed as when I run from the server. Feedback from IT is that they read through @BrettZimmerman pdf's and everything appeared proper. Will go back to SPM for a revisit (IT said everything was fine last summer). As a general comment, this server has always seemed slow. Server has 2008 R2 Standard for an OS with 8 GB memory. Doesn't appear to be under any processing load. Has 61 GB of free space on the D drive but only 3 GB of 80 GB on the C drive. I wonder if there is enough space to run the print queues and other background utilities?? DSN=SOTAMAS90;Description=MAS 90 4.0 ODBC Driver;Directory=\\192.168.1.2\Sage\v2017\MAS90;Prefix=\\192.168.1.2\Sage\v2017\MAS90\SY\, \\192.168.1.2\Sage\v2017\MAS90\== \;ViewDLL=\\192.168.1.2\Sage\v2017\MAS90\Home \;RemotePVKIOHost=192.168.1.2;RemotePVKIOPort=20222;CacheSize=4;DirtyReads=1;BurstMode=1;StripTrailingSpaces=1;SERVER=NotTheServer