FreeTDS Development Group

["Rui Ribeiro" <ruirib AT computer.org>]

> -----Original Message-----
> From: bounce-freetds-130046 AT franklin.oit.unc.edu
> [mailto:bounce-freetds-130046 AT franklin.oit.unc.edu]On Behalf Of Geoff
> Winkless
> Sent: quarta-feira, 20 de Junho de 2001 15:13
> To: TDS Development Group
> Subject: [freetds] Re: SQL Server Emulation
>
>
> "Michael Peppler" <mpeppler AT peppler.org> wrote:
> : I'll respectfully disagree that using stored procs is a bad idea.
> :
> : (yes it hurts portability, but it allows for better performance, for
> : data hiding, and for single location query tuning).
>
> I'd agree if the amount of portability issues were minimal but essentially
> once you've written a system to use MS SQL and SPs, you -cannot- move to a
> different database without a rewrite.
>
> That's not "hurting", that's repeatedly taking a very large sharp knife to
> the jugular.
>
> The performance gain does not justify the restrictions placed on the user
> thereafter.
>
> Geoff

I really wouldn't like to start a passionate discussion over the subject of 
stored procedures, but I
feel compelled to voice my agreement with Michael. We have a system used by 
more that a hundred
people. The use of stored procedures was essential to achieve the adequate 
performance. I don't
believe in making our users endure a low performance on the (very) remote 
possibility that I'll have
to migrate my database system in a remote future. Obviously you have to 
strike an adequate balance
between performance and portability, so it is not recomended that you use 
proper care in choosing
what to implement as a stored procedure. But they are instrumental in 
achieving adequate performance
in many ocasions. You just need to use common sense in your choice.

Rui