Hi,
I am assuming that a "forward_only" cursor is the same thing as a
"unidirectional cursor". Delphi's DBX uses unidirectional cursors as a
way of simplifying the engine. Then if you want "bidirectional cursors",
you can link the unidirectional cursor from a database to a bidirectional
"client cursor" (basically a local in-memory cache of a result set), and
operate on that. I wonder if this means that DBX+Delphi programs will
have significantly worse performance than BDE (the older,
windows-only)+delphi apps.
Thank you,
Noah Silva
IS&T - Programmer Analyst
(215) 419 - 7916
"Diesing, Burkhard" <[EMAIL PROTECTED]>
02/26/2003 10:20 AM
To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>,
[EMAIL PROTECTED]
cc:
Subject: RE: SAPDB vs. Microsoft SQL Server
Hi,
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 26, 2003 11:46 AM
To: Diesing, Burkhard; [EMAIL PROTECTED]
Subject: RE: SAPDB vs. Microsoft SQL Server
I'm happy to say : sapdb is very very faster in the other cursor-types.
I had responsetimes of about 2.7 seconds with sapdb vs over 25 seconds
with microsoft sql server.
But I'm not sure, why sapdb is as slow to perform a forward_only cursor
I am surprised too that the forward_only cursors are slower than the other
once. It should not.
Are there any updateable options set or does the result set size differs?
Please post a call trace or a SAPDB ODBC trace of your forward_only
scenario.
Regards,
Burkhard
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
