ODBC or ADO Connection String

Discussion in 'Computer Support' started by MadMike42, Feb 23, 2006.

  1. MadMike42

    MadMike42 Guest

    I'm trying to find a comparison chart for comparing
    the data access speeds for using VB6 with a SQL 2000
    System ODBC link (DSN) or using a direct ADO connection string (OLE DB)
    (this is for read / write data)
    I've found one chart on 4guysfromrolla but it only gives
    one example which is shown below, but im looking for
    some more examples.
    Any idea's ?

    Performance Comparison
    SQL Access
    Connection Times: 18 82 Connection Times: 62 99
    Iterating through 1,000 Records Times: 2900 5400 Iterating through
    1,000 Records Times: 100 950
    MadMike42, Feb 23, 2006
    1. Advertisements

  2. MadMike42

    why? Guest


    Try the database / odbc newsgroups. Maybe even the MSDN site , OTOH
    write your own test / timer routine.

    why?, Feb 23, 2006
    1. Advertisements

  3. I always found a direct ado connection string gave me less agrovation than a
    dsn in a web context using asp. Not sure which is faster but I imagine there
    is only a naggers cock worth of difference. Writing in VB6 (or VB for that
    matter) is never going to be the fastest in terms of performance (as it
    relies on the VB runtime library) so I would not split hairs. I would go
    with what gave reliable and steady performance myself, but we are all
    different. DSN is just something else you have to set up and define
    elsewhere whereas you can hard code an ADO connection string without
    worrying of getting a DSN set up. (although it's not difficult).
    Flunkett Clogwheel, Feb 23, 2006
  4. MadMike42

    MadMike42 Guest

    thanks for the comments.

    MadMike42, Feb 23, 2006
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.