Hi,
I have two questions concerning "weird" effects I encountered while working
with a SAPDB:

1. I access a database in a c++-program via ODBC. The program performs an
action that uses many SELECTs that return many rows. The action takes about
28 secs. Then I add an index to the database that contains a foreign key
that is used in a join in the SELECTs, and the same action takes only about
1.5 secs. Then I disable that index, and the same action takes about 3 secs.
How can that be? I repeated this, to be sure it isn't an effect of the
cache??

2. I use a stored procedure that is called by the program. It works fine.
Then I add a new column to a table that isn't even used in the stored
procedure. Now every call of the stored procedure causes the database to go
offline. Logfile dbm.prt says "command param_abortsession". Then I delete
and recreate the stored procedure and everything is fine again. Why?

Thanks in advance,

Florian K�rner

_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general

Reply via email to