Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (3)

Resolved Slow opening of SQL from DW Painter

  1. Issue
0
Votes
Undo
  1. Roland Smith
    Roland Smith
  2. InfoMaker
  3. Wednesday, 14 April 2021 13:18 PM UTC

We are on PB & IM 2019 GA. Database is SQL Server using ODBC connection.

One of our customers reports that in InfoMaker opening the SQL designer from the Report (DataWindow) painter is extremely slow, 8-10 seconds.

I had the same issue with PB 12.5 before the upgrade to 2019. I have no idea why I no longer have the slowness, the ODBC profile is the same.

Any ideas on the cause and how to fix?

Conditionally Show Fields in Form
QR codes in Infomaker
Responses (3)
Marco Meoni
Marco Meoni Accepted Answer Pending Moderation
  1. Wednesday, 14 April 2021 14:20 PM UTC
  2. InfoMaker
  3. # 1

Hi Roland,

4K monitor?

That happens to me too. One PC, 2 monitors: 1st monitor opening and usage ok, 2nd (4K) monitor slow.

Cheers,

.m

Comment
Roland Smith
  1. Roland Smith
  2. Wednesday, 14 April 2021 14:30 PM UTC
For me it was a laptop with lid closed and two 22 inch monitors that are not 4k.
  1. Helpful
There are no comments made yet.
Olan Knight
Olan Knight Accepted Answer Pending Moderation
  1. Wednesday, 14 April 2021 14:29 PM UTC
  2. InfoMaker
  3. # 2

This is normal. The more complex the SQL, the longer it takes to open the SQL Designer in the DW Painter.

If you've NOT seen that behavior, then please let the rest of us know how you did it!  :)


Later -

Olan

 

 

 

Comment
Load more comments
Olan Knight
  1. Olan Knight
  2. Wednesday, 14 April 2021 23:01 PM UTC
Oh, and we're connecting to our database using the native drivers provided by Powerbuilder, of course.
  1. Helpful
René Ullrich
  1. René Ullrich
  2. Thursday, 15 April 2021 05:30 AM UTC
Olan: This slowness with oracle is because of some changes in Oracle system views that powerbuilder uses to get information about tables and fields. You can accelerate it if you specify tablename for each column in SQL SELECT if you use more than one table in your query. So powerbuilder does not have to check each column name for each table. This makes the painter with large SELECTs slow (if you have 10 columns in SELECT from three tables PowerBuilder have to check 30 combinations to find out what column is from what table!)

So write SELECT TAB1.COL1, TAB2.COL2 instead of SELECT COL1, COL2.

  1. Helpful
Olan Knight
  1. Olan Knight
  2. Thursday, 15 April 2021 15:42 PM UTC
Ah HA! Thank you, Rene, for the explanation!
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 14 April 2021 18:58 PM UTC
  2. InfoMaker
  3. # 3

Hi Roland;

  Out of curiosity .. how long does it take to open the SQL Painter if you use the SNC (native) SS connection type in the IM IDE?

Regards ... Chris

Comment
Roland Smith
  1. Roland Smith
  2. Wednesday, 14 April 2021 19:12 PM UTC
I don't know, it is instant for me. I'm not sure of the details, I was just CC'd on an email thread.
  1. Helpful
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.