View Single Post

   
  #3 (permalink)  
Old 04-24-2008, 06:07 PM
John Bigbooty
 
Posts: n/a
Default Re: SQL Native Client vs SQL Server Driver

On Sun, 20 Apr 2008 18:38:08 -0400, "Sylvain Lafontaine" <sylvain aei
ca (fill the blanks, no spam please)> wrote:

>You are over-thinking here. First, you should think about finishing your
>application instead of trying to *optimize* it when it's not even finished.
>
>Second, trying to evaluate the relative performance of different drivers is
>a much more difficult task than you think. The results that you are now
>getting could be totally different on another system or on the same system
>but with a different level of load or of pattern of usage.
>
>Third, even if you could evaluate some difference between their performance,
>there are things more important than that: first, the real load on a
>sql-server is made by executing queries, not by returning the final result
>to the client and second, the added functionality and security provided by
>the latest driver if probably much more important than the possibility of
>saving a few microseconds here and there.
>
>Finally, if you absolutely want to save a few microseconds, add more memory
>or wait a few weeks before buying your next computer.


Was there some reason you felt compelled to reply and act like a total
ass? Before you go making blanket assumptions about me or my
application perhaps you should look in the mirror and ask yourself "am
I really as high and mighty as I think I am?"

First, my application is basically complete. We are just finishing the
final details and making sure we support both the SQL 2000 & 2005
platforms using the most efficient driver for client connections.

Second, although I'm concerned about server-side performance, that
wasn't the issue at hand. Since I need to support both 2000 and 2005
running mostly the same queries, I wanted to know what was the
recommended client side driver to use for an application that needs to
support both platforms.

Finally, we aren't talking about microseconds here. Our application
frequently runs complex queries against tables involving more than
10,000,000 rows. Adding memory or buying a new computer is not a
decision we make. We leave that up the hundreds of users purchasing
the software.

Mark
Atlanta GA


Reply With Quote