About DataSet and Stocked procedure performance

[# Cyrille37 #]

Hello,

I'm learning .Net's Dataset and TableAdaptor. They store data locally and only
propagate change to the SQL Server. That's a unconnected data access.

By this way, a question comes to me :

When we use Select() on a Table for a Dataset, it search for data locally.
But if we call a method which is an accessor to a Stocked Procedure, the
execution wil be done on the server isn't it ??

So, if I'm right : if we want better performance it should be better to not use
stocked procedure for Selecting data to avoid the server communication.

Am I right ? Or miss understood ?

Thanks for your explanation.
Regards,
Cyrille.

 

[Magnus]

Hello,

I'm learning .Net's Dataset and TableAdaptor. They store data locally and
only propagate change to the SQL Server. That's a unconnected data access.

By this way, a question comes to me :

When we use Select() on a Table for a Dataset, it search for data locally.
But if we call a method which is an accessor to a Stocked Procedure, the
execution wil be done on the server isn't it ??

So, if I'm right : if we want better performance it should be better to
not use stocked procedure for Selecting data to avoid the server
communication.

Am I right ? Or miss understood ?

Fetching data already in application memory is obviously alot faster than
returning data from a sql server over a communication link.

- Magnus