1. Thomas Rolseth
  2. PowerBuilder
  3. Friday, 26 August 2022 16:01 PM UTC

I have a client with about 10 or so 'super' users who often work remotely.  When they need to use the application (PB 2021), they RDP into a Windows 2019 Server desktop, launch the app that is deployed there and go about their daily work.  The application uses SQL Server 2019.  In mid-June, they moved to new servers and upgraded to SQL Server 2019 from 2014.  At first performance seemed fine.  In the last few weeks however, users have been reporting sporadic/intermittent performance issues.  I've looked in Task Manager/Performance Monitor/Event Viewer and don't see anything obvious.  Their network folks have checked things and don't seem anything amiss.  The client application connects to the SQL Server database using the new MSOLEDBSQL driver.

It doesn't explain the timing of the onset of performance issues, but it seems like it would be good idea to limit the number of users who can run this application on the this machine.  This made me think of PowerClient.  Would using PowerClient be a potential performance improvement over connecting to a VPN or Citrix and running the app from their office computers or laptops?

So, two questions:

  1. Are there any performance tuning tips or tricks or connection properties to try based on the scenario above?
  2. Is PowerClient faster than using a VPN, Citrix or RDP?

Thanks, Tom

Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Friday, 26 August 2022 16:59 PM UTC
  2. PowerBuilder
  3. # 1

Hi Tom,

PowerClient is still client/server architecture… only the install procedure is different.  So it wouldn’t give you any performance advantage using it on top of Citrix.  Also, connecting directly from remote machines to database over VPN not recommended either for performance and other reasons.  

PowerServer is our cloud-native architecture replacement of Citrix.  However, if as traditional client/server your app performs poorly then certainly PowerServer won’t help make things faster.

I think Chris may be on to something to investigate SQL Server itself since neither your PB version or source code has changed recently to make it possible culprit of the problem.

On a related note, we have gotten feedback from our beta testers that PB 2022 is noticeably faster than previous versions.  So even you solve this problem, it may be attractive to upgrade to 2022.

Best regards,


There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 26 August 2022 16:13 PM UTC
  2. PowerBuilder
  3. # 2

Hi Tom;

  Have you tried having your DBA rebuild the SS DB Statistics? Sometimes SS gets its processing messed up because it's trying to use an old "SQL Plan" for specific table(s) instead of building a new more optimized one. Especially after where the Truncate Table commands have been used previously.

FYI:  See sp_updatestats


Regards ... Chris

There are no comments made yet.
  • Page :
  • 1

There are no replies made for this question yet.
However, you are not allowed to reply to this question.