sql92 persistent connections

Posted by jmls on 28-Mar-2007 10:55

is there a way of making a client connection persistent ? I have the following in my db log, and it is everytime my linux sql client connects and reads/writes to the db.

TIA.

P-4432 T-5700 I SRV 27: (8873) Login usernum 537, remote SQL client.

P-4432 T-5700 I SRV 27: (7129) Usr 537 set name to SYSPROGRESS.

P-4432 T-5700 I SRV 27: (453) Logout by SYSPROGRESS on .

P-4432 T-2964 I SRV 27: (8873) Login usernum 537, remote SQL client.

P-4432 T-2964 I SRV 27: (7129) Usr 537 set name to SYSPROGRESS.

P-4432 T-2964 I SRV 27: (453) Logout by SYSPROGRESS on .

P-4432 T-4708 I SRV 27: (8873) Login usernum 537, remote SQL client.

P-4432 T-4708 I SRV 27: (7129) Usr 537 set name to SYSPROGRESS.

P-4432 T-4708 I SRV 27: (453) Logout by SYSPROGRESS on .

P-4432 T-5216 I SRV 27: (8873) Login usernum 537, remote SQL client.

P-4432 T-5216 I SRV 27: (7129) Usr 537 set name to SYSPROGRESS.

P-4432 T-5216 I SRV 27: (453) Logout by SYSPROGRESS on .

P-4432 T-3572 I SRV 27: (8873) Login usernum 537, remote SQL client.

P-4432 T-3572 I SRV 27: (7129) Usr 537 set name to SYSPROGRESS.

P-4432 T-3572 I SRV 27: (453) Logout by SYSPROGRESS on .

P-4432 T-2880 I SRV 27: (8873) Login usernum 537, remote SQL client.

P-4432 T-2880 I SRV 27: (7129) Usr 537 set name to SYSPROGRESS.

P-4432 T-2880 I SRV 27: (453) Logout by SYSPROGRESS on .

All Replies

Posted by jtownsen on 28-Mar-2007 11:00

I'm guessing that the sql client you're using is implicitly connecting / disconnecting with each request. If so, we'd need to know which client you're using. Perhaps there's a setting in the client - perhaps there isn't.

Posted by jmls on 28-Mar-2007 11:27

the sql client is the progress 10.1B odbc driver However, since I have set READ-COMMITTED, it doesn't seem to be reconnecting all the time.

Posted by jtownsen on 29-Mar-2007 07:32

With regards to the SQL Client, I was trying to ask what was using the ODBC driver, 'cos it might be doing the connect/disconnect. (eg. sqlexp - the OpenEdge SQL Explorer).

Glad you found a solution though.

This thread is closed