On TechRepublic: 10 cool USB flash drive tricks
BNET Business Network:
BNET
TechRepublic
ZDNet
TalkBack 17 of 34:
Next »
« Previous
Varying opinions
There are varying opinions. Stored procedures are tied to the database and thus make the database part of the application. Since the stored procedures are database spesific, you can't copy them between different database vendor products.

If you are selling packaged software, you don't want anything to do with stored procedures for that particular reason. You want your stuff to work on many databases.

If you are developing software for a company that has vendor independence requirements like many companies do, then you better make software that runs on all major databases. These companies want to keep the vendors on their toes to negotiate the best price. If you are married to one vendor, you have no good way to negotiate, and have to cough up the 'extortion premium'. These days, that does not fly.

What comes to writing database software - you don't have to write inline SQL at all. You can have all queries tucked away in config files (xml for example). Nothing is copied or duplicated.

So it is a matter of taste, within one application, if you are going to use stored procedures or not. Sometimes you have to use them because they solve problems that inline sql does not (performance, some heavy lifting in database that has to do with organizing data). In general, there is no significant performance advantage for simple stored procedures, so using them boils down to convenience and often it is more convenient to do the work in a proper programming language.
Posted by: tero_t_vaananen@...   Posted on: 11/01/05 You are currently: a Guest | Members login | Terms of Use

Alert moderator to an offensive message

Subscribe to this discussion via Email or RSS

I brought this up  Roger Ramjet | 10/31/05
PAPPL?  jpratch | 10/31/05
Its just another trick  Roger Ramjet | 10/31/05
I don't mind, with some reservations  Mark Miller | 10/31/05
Debugging tools for PHP  eheimer | 11/01/05
So what's wrong with Fortran?  Gravitas@... | 10/31/05
Like what?  Not average Joe | 10/31/05
Like handcuffing your code to specific hardware  Robert Kohlenberger | 11/01/05
Right on the Money RK  tbbrickster_z | 11/02/05
Productivity writing assembler?  cgraham_z | 11/03/05
Agree that Database Procedures are Evil  daver_z | 10/31/05
Maybe for small applications  Yensi717 | 10/31/05
OOD  Gravitas@... | 10/31/05
I think  Yensi717 | 10/31/05
Spot on right  Justin James | 10/31/05
Yeah, well...  emofine | 10/31/05
Varying opinions  tero_t_vaananen@... | 11/01/05
Right on.  zztong | 11/01/05
Multiple database vendors  Yensi717 | 11/01/05
Not a pain to edit  Chad_z | 11/01/05
Great framework  bkatz | 10/31/05
Looked like a pain to me...  Justin James | 10/31/05
For Unix deployments you might consider...  Mark Miller | 10/31/05
Message has been deleted.  khakman | 10/31/05
I've heard of Ruby  CobraA1 | 10/31/05
You mean like Smalltalk?  wkharold | 10/31/05
Funny  John Carroll ZDNet Moderator | 10/31/05
true  jimk_z | 10/31/05
true  jimk_z | 10/31/05
Ruby is OO  tero_t_vaananen@... | 11/01/05
Just what are people spouting about?  jacec | 10/31/05
Are there other benefits?  DougOfCBS ZDNet Moderator | 11/01/05
This is not serious development  SQLDBAJames | 05/29/06
Not everything is a nail  rarsa | 11/03/05

What do you think?

SponsoredWhite Papers, Webcasts, and Downloads

advertisement
advertisement

SmartPlanet

Click Here