I would have to agree with you. The kinds of applications you mentioned need every
scrap of speed possible. All I was saying is that stored procedure use is a trade off
of flexibility vs. performance. In many applications the flexibility is more important
than the performance gain and that the
The fundamental reason for using stored procedures is performance.
Stored procedures are compiled code. This means the database has reviewed the SQL,
came up with the most efficient plan of action (often sorting through thousands of
permutations when multiple table joins are concerned), and (giv
The concept of n-tier design is mainly one of flexibility. A proper n-tier design
should allow you to change either the front-end, business logic or back end (database)
with no (or minimal) changing of the other layers. This means that the user interface
(front end) is one layer (local exe, web
Quoting Mike <[EMAIL PROTECTED]>:
> One thing to remember is that every stored procedure you execute steals
> resources that would otherwise go to handling queries, so you do not
> necesscarily see a performance boost by using stored procedures for
> everything, in fact a MySQL server handling a
>So what are the justifications? What makes a wise stored procedure
>and an unwise stored procedure?
Use them when there is a real benefit to using stored procedures. I will give one
example when I would have used them:
With a CRM solution I once wrote, I wanted to get a list of n randomly sel
All IMHO of course...
> > Will I use them in MySQL 5.0? Probably, but only when justified.
> >
> >
>
> So what are the justifications? What makes a wise stored procedure and an
> unwise stored procedure?
I've used them a lot with Oracle. The n-tier days weren't really alive
when I was doing that
Original Message -
From: "robert_rowe" <[EMAIL PROTECTED]>
>
> Will I use them in MySQL 5.0? Probably, but only when justified.
>
>
So what are the justifications? What makes a wise stored procedure and an
unwise stored procedure?
--
MySQL General Mailing List
For list archives: http:
Back to stored procedures for a second. I use them with MSSQL. For certain tasks they
greatly improve performance because I don't have to move all the data client side. For
the vast majority of tasks though stored procedures yeild little performance gain.
I've seen systems that (designed as M
> Obviously, the details are vague here, I was just wondering if anyone had
> any stories, personal ones, rather than the press announcements, of adopting
> MySQL for line of business, critical stuff - what it involved, how it went,
> what issues they faced in getting it accepted and so on.
>
> I'
As I understand stored procedures:
Stored procedures offer a level of performance that you normally can not
replicate in code. The stored procedure actually has the query stored in the
query parser ready to rumble. You do not have to invoke network or socket
overhead in calling a long query and yo
m soap box]
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, January 06, 2004 10:01 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Bet the Business
>
>
> Quoting robert_rowe <[EMAIL PROTECTED]>:
>
> >
> > I'm
Quoting robert_rowe <[EMAIL PROTECTED]>:
>
> I'm lead developer for a company that writes custom software for the mining
> industry. We support MSSQL and MySQL. I've found that from a programming
> aspect (VB + ADO) there is relatively little difference between MSSQL and
> MySQL. There is some si
I'm lead developer for a company that writes custom software for the mining industry.
We support MSSQL and MySQL. I've found that from a programming aspect (VB + ADO) there
is relatively little difference between MSSQL and MySQL. There is some sight syntax
differences and MySQL versions < 5.0 d
Ian ORourke said:
>
> In the near future we face making a decision for a database backend,
> and the logical choice for us is MSSQL as we have one server already
> for Great Plains - but it would seem MySQL is much cheaper.
Perhaps. But supporting 2 database servers sounds like the most
expensive
Ian O'Rourke wrote:
I've been playing with MySQL for a bit now (and it is playing) and I'm using
it for a number of personal sites (ie not many users, and only I really post
stuff). I've also adopted it at work, and we use it to dump Lotus Domino
information into for more structured reporting. All
I've been playing with MySQL for a bit now (and it is playing) and I'm using
it for a number of personal sites (ie not many users, and only I really post
stuff). I've also adopted it at work, and we use it to dump Lotus Domino
information into for more structured reporting. All is good.
In the nea
16 matches
Mail list logo
