Hello,
We are running a weblogic application that opens connection pools on ASE, all connections have the same default database.
The connections run their update queries from the default database (they don't execute use database commands to go to the database in which the majority of the tables that are updated by the transaction resides), so all transactions are cross-database transactions.
This is causing some contention on the transaction log.
The database doesn't contain any data/tables (in the past we created this database to avoid that weblogic's default database is a database that is also replicated).
We want to set 'delayed commit' to true for this database, but I'm wondering if this will be limited to the default database and will handle cross database transactions correctly.
Any experience with this ?
Thanks,
Luc.