SQL Anywhere database - Connect a Delphu Client to ASA

Author

Connect a Delphu Client to ASA

Ephraim

2005-08-24, 7:23 am

I wish to control transaction client-side and I am using ODBC.
Are the correct settings
AUTOCOMMIT=OF and CHAINED=ON?

Furthermore what tools are available to monitor transactions, SQL Commands
from for all/a specific connection ?

TIA

Ephraim

Greg Fenton

2005-08-25, 3:31 am

Ephraim wrote:
> I wish to control transaction client-side and I am using ODBC.
> Are the correct settings
> AUTOCOMMIT=OF and CHAINED=ON?

Turning AutoCommit to OFF gives you client-side control of transactions.
Chained mode you want left ON (it is a T-SQL compatibility
option...don't bother playing with it unless you are trying to emulate
ASE/MSSQL behaviour).

> Furthermore what tools are available to monitor transactions, SQL Commands
> from for all/a specific connection ?

Please always post the version and build number of SQLAnywhere that you
are using.

Take a look at "Request-Level Logging" in the SQLAnywhere 9.x online docs:

ASA SQL User's Guide
Monitoring and Improving Performance
Performance analysis tools
- Request logging

greg.fenton
--
Greg Fenton
Consultant, Solution Services, iAnywhere Solutions
--------
Visit the iAnywhere Solutions Developer Community
Whitepapers, TechDocs, Downloads
http://www.ianywhere.com/developer/

Ephraim

2005-08-25, 7:23 am

ASA 9.0.2.2542

AutoCommit was already turned OFF It was only by turning CHAINED ON that I
could control the transaction from the Cliemt.

If I aborted between to commands within a transaction with Chained OFF the
first was Committed with Chained ON it was n't. The docs. imply thta
AutoCommit should control (as its name suggests) but testing shows
otherwise!!!

TIA

Ephraim

"Greg Fenton" <greg. fenton_NOSPAM_@ianyw
here.com> wrote in message
news:430d3734$1@foru
ms-1-dub...
> Ephraim wrote:
>
> Turning AutoCommit to OFF gives you client-side control of transactions.
> Chained mode you want left ON (it is a T-SQL compatibility
> option...don't bother playing with it unless you are trying to emulate
> ASE/MSSQL behaviour).
>
Commands[color=darkr
ed]
>
> Please always post the version and build number of SQLAnywhere that you
> are using.
>
> Take a look at "Request-Level Logging" in the SQLAnywhere 9.x online docs:
>
> ASA SQL User's Guide
> Monitoring and Improving Performance
> Performance analysis tools
> - Request logging
>
> greg.fenton
> --
> Greg Fenton
> Consultant, Solution Services, iAnywhere Solutions
> --------
> Visit the iAnywhere Solutions Developer Community
> Whitepapers, TechDocs, Downloads
> http://www.ianywhere.com/developer/

Greg Fenton

2005-08-26, 3:23 am

Ephraim wrote:
>
> If I aborted between to commands within a transaction with Chained OFF the
> first was Committed with Chained ON it was n't. The docs. imply thta
> AutoCommit should control (as its name suggests) but testing shows
> otherwise!!!
>

I find the docs on the CHAINED option make it quite clear. From the
SQLAnywhere 9.x online docs:

ASA Database Administration Guide
Database Options
Alphabetical list of options
- CHAINED option [compatibility]

"... In Unchained mode (CHAINED = OFF), each statement is committed
individually unless an explicit BEGIN TRANSACTION statement is
executed to start a transaction."

If you think there is a section of the documentation that is misleading,
please post the particular section and I'll forward it to the
documentation team.

Thanks,
greg.fenton
--
Greg Fenton
Consultant, Solution Services, iAnywhere Solutions
--------
Visit the iAnywhere Solutions Developer Community
Whitepapers, TechDocs, Downloads
http://www.ianywhere.com/developer/

Sponsored Links