1. Clarence Chamorro
  2. PowerServer Web
  3. Sunday, 14 October 2018

Good morning,

I have an issue. It could be because my no much experience with PowerServer. He it goes:

Why is it if I have PowerServer Data Source Dynamic Database Connection turn off the apps connect to the database performance is supppppeeerrr fassssttttt. Vrs if I have the Data Source Dynamic Database Connection turn on the apps connection to the database performance is super slow? 

This is my actual connection code:

//cch if it is window's client

If AppeonGetClientType() = 'PB' Then
  SQLCA.DBMS = "ODBC"
  SQLCA.AutoCommit = False
  SQLCA.DBParm = "ConnectString='DSN=arazoza_prod17;UID=;PWD=;UID=" + Trim(istr_gen.username) +     ";PWD="+ Trim(istr_gen.userpassword) +"',cachename='arazoza_prod17'"
Else

//cch if is mobile or web's client

  SQLCA.DBMS = "ODB-asa"
  SQLCA.AutoCommit = False
  SQLCA.DBParm = "cachename = 'arazoza_prod17'"
  SQLCA.LogId = Trim(istr_gen.username)
  SQLCA.LogPass=Trim(istr_gen.userpassword)

End If

do I have to add any other parameter so it connect as fast as if I have the Data Source Dynamic Database Connection turn of.

Like always regretful of your help.

Regards,

Clarence. 

Marco Meoni Accepted Answer Pending Moderation
0
Votes
Undo

Hello,

what's your DB? From the transaction parameters I guess it is ASE 17.

Did you select (from Appeon help): "SQL Anywhere 17 Native Driver" to connect with SAP SQL Anywhere 17.0 databases;"? Older versions have instead "SQL Anywhere Native Driver".

The error in your screenshot usually comes after a DB connection timeout upon unsuccessful login.

 

Best,

.m

Comment
SQL AnyWhere 17.0 database. using the "SQL Anywhere 17 Native Driver".



The funny thing is that after the error we tap ok and try again and it connect immediately.
  1. Clarence Chamorro
  2. Monday, 15 October 2018
There are no comments made yet.
  1. Monday, 15 October 2018
  2. PowerServer Web
  3. # 1
Chris Pollach Accepted Answer Pending Moderation
0
Votes
Undo

Hi Clarence;

  This does not sound right to me. In the golden oldy days of C/S, a DB connect was a very expensive command to process. However, in this past decade - high speed networks, better routers, improvements in DNS resolution etc have (in my recent testing) placed the DB Connect as an almost negligible over-head.

   This sounds to me like it might be an issue within PS itself. as waiting even more than 1-2 seconds for a DB Connect - never mind a minute plus - would seem extreme to me. I would suggest opening a Support Ticket on this issue. I suspect that the Appeon Support team will then request PS traces that should hopefully, narrow down this negative performance phenomenon. 

Regards ... Chris

Comment
I will open a support ticket as you recommend.
  1. Clarence Chamorro
  2. Monday, 15 October 2018
Please note that SQL Anywhere 17.0 build 2000 through build 4881 may experience slow connection performance (not in minutes but seconds in our testing). SQL Anywhere introduced a secure password exchange feature which could perform slowly on Windows platforms depending on the source of the connection. We identified that the encryption gear used in SA had an inefficient algorithm. This has been fixed. I would update to SQL Anywhere 17.0 SP0 PL36 Build 4897 to pick up that fix.
  1. Chris Keating
  2. Thursday, 15 November 2018
There are no comments made yet.
  1. Monday, 15 October 2018
  2. PowerServer Web
  3. # 2
Clarence Chamorro Accepted Answer Pending Moderation
0
Votes
Undo

I agree with you guys it should take a little longer. But What I'm experimenting is minutes to do the connection.

The first time the app tries to connect with the database & after couple of minutes trying to connect I get this error: "Error Occurred In Appeon Communication Layer. Possibles Causes: 1. The Network is unstable or disconnected. 2. Appeon Server does not work. 3. The PB Coding Style is undefined."

I attached the screen picture of the error.

The estrange thing is that the second time I enter User id & Password it connects supper fast and no error. Everything work perfect.

What it could be? I will appreciate your comments and advises.

 

Attachments (1)
Comment
There are no comments made yet.
  1. Monday, 15 October 2018
  2. PowerServer Web
  3. # 3
Marco Meoni Accepted Answer Pending Moderation
0
Votes
Undo

Hello,

That's because each time you start a session you create a new (dynamic) connection pool for the given Trim(istr_gen.username) rather than reusing same pool for all sessions.

Best,

.m

 

Comment
There are no comments made yet.
  1. Monday, 15 October 2018
  2. PowerServer Web
  3. # 4
mike S Accepted Answer Pending Moderation
0
Votes
Undo

if you use dynamic database connection then powerserver actually connects to the database for that session/user instead of using one of the existing shared connections from the pool.  so using a connection pool (dynamic OFF) would usually be faster for the actual connection, although once connected i would think the speed should be the same/similar.

 

Comment
There are no comments made yet.
  1. Sunday, 14 October 2018
  2. PowerServer Web
  3. # 5
  • Page :
  • 1


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