I have a strange scenerio happening. Here's the details:

I'm connecting to SQL 7.0 using ODBC from an ASP
application on a separate web server.

This ASP connection calls a COM+ object which only serves
as a middle man for connectivity. (Doesn't actually house
its own query strings)

Anyway, on one particular stored proc that I call, I
receive a 'timeout expired' message back from SQL.
However, I CAN run the procedure under a few different
circumstances:

A) I create a new, identical stored procedure with just
a different name and use it instead

B) I create a new index and change the hardcode in the
current stored proc to use that index.

C) I add the command 'With Recompile' to the end of my
stored proc query string.


Each of these options will successfully allow me to run
the stored proc for my ASP page. I don't have ANY issues
if I run the stored proc from Query Analyzer.

So my question is... WHY the fickle, anal response from
SQL 7.0? It ONLY happens from my ASP page, and I can
solve it by the most stupid tactics (ie. change the
stored proc name to a new identical stored proc, or
add 'with recompile). This truly makes no sense, and is
obviously a bug. Has anyone ever hear of it before?
Know the solutions?

My SQL 7.0 box is fully updated with MDAC 2.7 SP1 and SQL
SP4. It's on Win Advanced Server 2000 wich also is fuly
updated.

My IIS box runs IIS 5.0 on Win 2000 Server, which is
fully updated. (Including MDAC)

My COM+ component is well coded with no issues anywhere
else, and by the way, uses MDAC 2.7

Thanks