geeks at sunhelp.org
Sun Aug 26 21:48:17 CDT 2001
So, to rephrase it - it seems that it is a way to implement on the database
server logic that can not be implemented in SQL...
Interesting, but not great, in my opinon - SQL is *very* flexible, and
almost any query should be able to be appropriately refined if done
When I studied DB/2, the course was taught by IBM, and their advice was to
do as much as possible *in the database", and that as IBM improved the SQL
optimizer, DB queries would get faster. They strongly discouraged
end-user/programmers from learning too much about how the optimizer worked,
becuase they wanted free reign to implement improvements as they saw fit,
without having to educate end user/programmers on the changes.
What I really hear in your example Josh, is that it is a way to implement a
three-tier application, with only two physical tiers...
Thanks for the insight, I never get involved with this stuff...
----- Original Message -----
From: "joshua d boyd" <jdboyd at cs.millersville.edu>
To: <geeks at sunhelp.org>
Sent: Sunday, August 26, 2001 10:20 PM
Subject: Re: [geeks] Databases
> I could be off base, but...
> When I've used them (mainly because a similar one was already written), I
> was told that they would run faster on the server than downloading and
> processing in VB could occur.
> Further (and I am fairly sure of this), they save network
> traffic. For instance, if a regular SQL SELECT can only narrow the field
> of records to return to 1 million, but you really only need 20, then the
> stored procedure could do the work and only transmit the 20 needed. But,
> when I did stored procedures, they were run so rarely (maybe
> monthly?) that it wasn't a significant savings.
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
More information about the geeks