Marco,
  Actually, that is the best way to go.  Here is something that I've
found to be useful as well:

In .NET if you want to execute a stored procedure you have special
stored procedure functionality where you need to declare all the input
variables ahead of time and they need to have the same name as they do
in the actual stored procedure and other things that just require a lot
of overhead. 

I prefer to use the SQL execute command and then I call the .NET SQL
Query call.

-- used to be
string mySQL =3D "Select * from myTable Where col1=3D'inVar1' and
col2=3D'inVar2'

--Now I use (it's the same for SQL server and Oracle)
String mySQL =3D "exec spMyStoredProcName 'inVar1', 'inVar2'"



Thomas A Degen
Project Analyst
Information Technologies
Journal Sentinel Inc.
(xxx) xxx-xxxx
TDegen@J...


<--- original message --->

 Hi all,

I am doing an application in .NET.=3D20

Could anyone tell me if there is something wrong if I do all of my =3D
queries via store procedures.  Is there any impact in performance?.  =3D
Does it depend on the DBMS I am using, e.g. Oracle or SQL server 2000?

Thank you in advance,
Marco.