Hendra
Unless you're talking about millions of records, I don't see a need to use a stored procedure for a SELECT since no action is done on the data. In fact, a view might be better so you can control which columns are being returned. As for the rest, it is usually quicker to let the SQL engine do the work directly for high-use routines when a large number of records are involved.
Bill Mosca
---In MS_Access_Professionals@yahoogroups.com, <agesthahendra@ymail.com> wrote:
Hi Everyone... :)
Is that wise to rely every process Select, Insert, Update, Delete based on Sql Server Stored Proc?
I really like the technique that using Pass Through Query to exec. the SP on Sql Server...so i'm starting thinking to do all DML and Select processes based on that technique as far as it can do the task,,,please give some advice...it would be very appreciated.
Regards
Hendra Agestha
Is that wise to rely every process Select, Insert, Update, Delete based on Sql Server Stored Proc?
I really like the technique that using Pass Through Query to exec. the SP on Sql Server...so i'm starting thinking to do all DML and Select processes based on that technique as far as it can do the task,,,please give some advice...it would be very appreciated.
Regards
Hendra Agestha
__._,_.___
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (2) |
.
__,_._,___
Tidak ada komentar:
Posting Komentar