By default, the data source manager runs a stock query to verify that connections are ready for use before placing them back in the data source pool. Sanity checking prevents errors that occur when components release a connection that is not ready for use by another component. For example, there may be pending results on the connection, causing an error when the next component to use the connection tries to send a command.
If you have debugged the results handling in your application, you can improve performance by disabling Ping Pooled Connections in the data source properties.
If you have enabled the Set Session Authorization property so database work runs under the effective user ID of the client, you can also enable the Ping With Set Session Auth property (pingAndSetSessionAuth). Doing so causes the ping and session-authorization commands to be run in a single command batch and may improve performance.
