What interface to use for a new application
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 9 of 9

Thread: What interface to use for a new application

  1. #1
    Join Date
    Sep 2000
    Location
    Chicago, IL
    Posts
    316

    What interface to use for a new application

    We will be developing a new App for very high volume inserts (1000 to 5000/sec). We may use some caching in the middle, so that the app does not wait for commits on Oracle.

    I know these are my choices:
    JDBC Thin Driver, OCI, OCCI, ODBC, OLE DB

    From your experience, which one would you recommend and why (I'm looking for the fastest performance)?

  2. #2
    Join Date
    Sep 2002
    Location
    England
    Posts
    7,333
    which ones do you know about, can code in and debug.

    If I had my choice ODBC would be outlawed though - it is slow

    Better yet have all the code in the database the accepts arrays of number, no sql in the middle tier

  3. #3
    Join Date
    Sep 2000
    Location
    Chicago, IL
    Posts
    316
    Our developers can code in JDBC, OCCI, ODBC (and I agree with your idea of the future of ODBC also) ...

    The architecture team has decided to go with Win2003 with C++ - so I guess it has to be OCCI; but I was wondering about my choices.

  4. #4
    Join Date
    Sep 2001
    Location
    Makati, Philippines
    Posts
    857
    I have to agree with Davey.
    I'd like to do coding more from server.

    forget odbc/ole db.

    OCI/OCCI for C/C++ will take more development time due to referrences. But that's depends on the expertise of your developers.

    If I were to make a choice, I will prefer JDBC and Java.
    Due to reasons like portability of codes, referrences, performance is considerable, ease of maintenance after implemented(not much bugs to occur) and it's the IN thing for me in the development circle right now. But that's just me.

  5. #5
    Join Date
    Aug 2000
    Location
    Jolo, Sulu
    Posts
    639
    Hi Huns,

    How about HTMLDB? can it be considered too

  6. #6
    Join Date
    Aug 2002
    Location
    Colorado Springs
    Posts
    5,253
    I don't see why waiting for commits is going to prevent you from reaching that target -- commit is extremely fast in Oracle. It seems an odd thing to focus on -- I'd be thinking more about the need to use low latency connections and bulk binding.

    Like davey says, which ones do you know about? And where are you going to place your logic? If you want to reduce roundtrips to the database then put your logic into PL/SQL packages and call them with OCI.
    David Aldridge,
    "The Oracle Sponge"

    Senior Manager, Business Intelligence Development
    XM Satellite Radio
    Washington, DC

    Oracle ACE

  7. #7
    Join Date
    Sep 2001
    Location
    Makati, Philippines
    Posts
    857
    Originally posted by kris123
    Hi Huns,

    How about HTMLDB? can it be considered too
    for bulky inserts? NO.

  8. #8
    Join Date
    Aug 2000
    Location
    Jolo, Sulu
    Posts
    639
    No, for OLTP thats what most application is doing. I would always use
    sqlloader direct path for bulk inserts

    Ms C3

  9. #9
    Join Date
    Sep 2001
    Location
    Makati, Philippines
    Posts
    857
    Originally posted by kris123
    No, for OLTP thats what most application is doing. I would always use
    sqlloader direct path for bulk inserts

    Ms C3
    I'm referring to this:
    We will be developing a new App for very high volume inserts (1000 to 5000/sec). We may use some caching in the middle, so that the app does not wait for commits on Oracle.

Posting Permissions

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


Click Here to Expand Forum to Full Width