Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. .NET (Core and Framework)
  4. Oledb or Odbc

Oledb or Odbc

Scheduled Pinned Locked Moved .NET (Core and Framework)
oracleperformance
2 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • N Offline
    N Offline
    NasimKaziS
    wrote on last edited by
    #1

    can anyone pls say in what kind of a scenario can i go for System.Data.Oledb and System.Data.Odbc. Is there any difference in their performance. will it suit well for Oracle. ----------------------------------------------------------------

    where there is a will there is a way

    R 1 Reply Last reply
    0
    • N NasimKaziS

      can anyone pls say in what kind of a scenario can i go for System.Data.Oledb and System.Data.Odbc. Is there any difference in their performance. will it suit well for Oracle. ----------------------------------------------------------------

      where there is a will there is a way

      R Offline
      R Offline
      Robert Rohde
      wrote on last edited by
      #2

      Hi, generally those are two different abstraction layers mainly doing the same thing. When trying to decide which one to use you should at first look for which one a driver for the target db is available. In the case of Oracle you could use both. If I remember correctly OleDb was faster, but this only matters if you fetch large amounts of data from the db. If you know you are using Oracle and you also know you will never switch the database engine than have a look at ODP.NET[^]. It's an implementation of the common ADO.Net interfaces which comes directly from Oracle and is (naturally) faster than the other two. It also has some more Oracle specific functionalities. The biggest drawback is that you can only access Oracle with it and nothing else. Robert

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups