|
I have an external stored procedure and call a stored procedure located at remote database server. I would like to know how to drop that connection after the call done. thx! |
|
What version of SQL Anywhere are you using? If you are using SQL Anywhere 16, then consult the documentation for the DROP REMOTE CONNECTION statement. If you are using SQL Anywhere 12 or below, then look at the CONNECTION CLOSE clause on the ALTER SERVER statement. the statement was applied, but the connection is still there and the request type becomes CONNECT_POOL_CACHE. Why?
(22 Aug '13, 18:57)
pLee
Replies hidden
1
The connection has been cached at the database server for efficiency reasons (in case you make another connection request in a short amount of time - 60 seconds, by default). See "Connection Pooling" http://dcx.sybase.com/index.html#sa160/en/dbadmin/sa22c8e99f-db62-4851-a551-ea775eeed6e8.html and "sa_conn_info": http://dcx.sybase.com/index.html#sa160/en/dbreference/sa-conn-info-system-procedure.html
(23 Aug '13, 08:25)
Jeff Albion
|
