Professional Web Applications Themes

strange myODBC / ADO / speed problem...help! - MySQL

Removed by Administrator...

  1. Moderated Post

    Default strange myODBC / ADO / speed problem...help!

    Removed by Administrator
    vanwout@gmail.com Guest
    Moderated Post

  2. Moderated Post

    Default Re: strange myODBC / ADO / speed problem...help!

    Removed by Administrator
    Thomas Guest
    Moderated Post

  3. #3

    Default Re: strange myODBC / ADO / speed problem...help!

    Hi Thomas,

    Thanks for your message....
    I just spent 30 minutes on the internet to search try to understand
    your suggestion...
    How do I define a passthrough query in ASP with mySQL?

    However, even if the passthrough query works, and this will be very
    interesting for me to learn, it still doesn't explain how all of a
    sudden the speed of the application plunged; and what I can do about it
    to fix it....

    Thanks!
     

    vanwout@gmail.com Guest

  4. #4

    Default Re: strange myODBC / ADO / speed problem...help!

    On Wed, 20 Sep 2006 00:13:12 -0700, vanwout wrote:
     

    I know nothing of ASP. You must be using the Microsoft DAO or ADODB
    libaralibraries. When you initiate your database or connection object,
    you have the opportunity to add a dbSQLPassthrough switch that indicates
    you want the system to pass the raw query through and let the the server
    interpret the SQL and return the result set.

    One trick I have resorted to is to use MS Access (.mdb) files. You can
    create stored queries tagged as PassThrough. From there you can just
    treat it like an ordinary Access database. The SQL in the query will
    simply be sent to the server without interpretation by Microsoft and you
    get the results back in a recordset. You can even dynamically alter the
    SQL inside the querydef objects (in the Access .mdb file!), throwing
    different MySQL legal queries into it. This is *mucho mas* faster that
    letting ADO interact with MySQL directly.
     

    That's a question for Microsoft.
     

    In my case, I have found the solution in falling back to older ADO library
    ..dll(s) and blocking automated Microsoft updates.

    This is not wonderful. The more viable, long term solution for me is to
    abandon attempts to mix Microsoft with non-Microsoft technologies (such as
    MySQL). For me this means Microsoft gets the boot. I can't deal with
    building my stuff on foundations of loose sand.

    Sour grapes aside. You would probably get better results and better
    responsiveness from Microsoft if you stick with all Microsoft technology
    like SQL server or whatever the heck it is they push nowadays.

    Thomas Bartkus


     [/ref]
    Thomas Guest

Similar Threads

  1. MyODBC on OSX 10.4
    By Al in forum MySQL
    Replies: 0
    Last Post: March 26th, 02:59 PM
  2. Datagrid speed problem
    By Sergei_T in forum Macromedia Flex General Discussion
    Replies: 3
    Last Post: September 29th, 09:13 PM
  3. FW MX2004: speed problem
    By Tudor M. Vedeanu in forum Macromedia Fireworks
    Replies: 9
    Last Post: October 13th, 09:15 PM
  4. Speed Problem on different databases using ASP.NET
    By Viktor Elvar in forum ASP.NET General
    Replies: 2
    Last Post: July 7th, 12:55 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139