Stored Procedure takes forever

Question

Hi!
I'm pretty new to stored procedures, but I was told it was a smart thing to implement in you application. So I tried.
I wrote a simple procedure with two inputs and one output as ref_cursor. I then bind it to a datagrid. Here's the procedure:
( B_CURSOR OUT NG_TYPE.NG_CURSOR,
gnr IN INTEGER,
bnr IN INTEGER
AS
BEGIN
OPEN B_CURSOR FOR
select kbydnr from vbmak
where kgrdnr = gnr
and kedmbnr = bnr
and rownum <= 10;
END GETBID;
As you can see it gets the data from a view.
I then timed the execution of the procedure, and the fastest time I got was 71 seconds!!!! Is there anything wrong here????
I tried the same thing with the NILE3 database sample (if anyone knows it). The procedure I ran there was almost identical:
P_CURSOR OUT NILE_TYPES.NILE_CURSOR,
SUBJECTIDIN INTEGER
AS
BEGIN
OPEN P_CURSOR FOR
SELECT BOOKID, BOOKTITLE, AUTHOR, PRICE, RETAIL
FROM PRODUCTS
WHERE SUBJECTID = SUBJECTIDIN
AND ROWNUM <= 10;
END LISTBYSUBJECT_SAMPLE;
see?
I took 15 milliseconds to run!
The asp.net code for these two are the same:
myTimer.StartTimer()
     gabCom.Connection = Conn
     gabCom.CommandType = CommandType.StoredProcedure
     gabCom.CommandText = "GETBID"
     gabCom.Parameters.Add(New OracleParameter("B_Cursor", OracleType.Cursor, 2000, ParameterDirection.Output, True, 0, 0, "", DataRowVersion.Default, myDBNull))
     gabCom.Parameters.Add(New OracleParameter("GNR", OracleType.Int32, 0, ParameterDirection.Input, True, 0, 0, "", DataRowVersion.Default, myDBNull))
     gabCom.Parameters.Add(New OracleParameter("BNR", OracleType.Int32, 0, ParameterDirection.Input, True, 0, 0, "", DataRowVersion.Default, myDBNull))
     gabCom.Parameters(1).Value = 57
     gabCom.Parameters(2).Value = 400
'bind the result to the datagrid:
     gab.DataSource = gabCom.ExecuteReader()
     gab.DataBind()
'stops the timer and display the time
     myTimer.StopTimer()
     lblGAB.Text = myTimer.GetTime()
Did I do something wrong here or is stored procedures not really the thing afterall???
I'm using MS Dataprovider for Oracle (version thingy, see)

Answer 1

Hi!
A select on one table takes long time, a select on another table takes much less time. These differences don't have anything to do with stored procedures or ASP.NET-Code.
start tuning your statements! Before programming the client. - What are the differences between the two tables?, what's about indexes on the columns? Are both tables anaylsed so that the CB-Optimizer can work out a good execution plan?
If you haven't found the reason after all that, try to trace the execution of the statements; right from the application, where you measured the difference in time.
Greetings!
G.Bonin