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. Comparison of '.NET SqlClient' and 'Microsoft OLEDB' for accessing MSSQL 7 and above

Comparison of '.NET SqlClient' and 'Microsoft OLEDB' for accessing MSSQL 7 and above

Scheduled Pinned Locked Moved .NET (Core and Framework)
sql-servercsharpdatabasesysadminquestion
3 Posts 3 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.
  • U Offline
    U Offline
    Uday Takbhate
    wrote on last edited by
    #1

    In the .NET documentation Microsoft is recommending usage of SQL server .NET data provider for accessing MSSQL 7 and above. Will any one please tell me what are the advantages of using .NET library over OLEDB? Uday

    A 1 Reply Last reply
    0
    • U Uday Takbhate

      In the .NET documentation Microsoft is recommending usage of SQL server .NET data provider for accessing MSSQL 7 and above. Will any one please tell me what are the advantages of using .NET library over OLEDB? Uday

      A Offline
      A Offline
      Anonymous
      wrote on last edited by
      #2

      Its recommened to use SQL Server .NET data provider because its made strictly for SQL Server and supports all its features. the OleDb.NET provider is a general provider and can be used for connectivity to any database Sql Server, Access, Oracel, etc... Similarly you should use the Oracle.NET dataprovider for connecting to oracle. There are finer points than what I've mentioned but that the bird's eye view.

      W 1 Reply Last reply
      0
      • A Anonymous

        Its recommened to use SQL Server .NET data provider because its made strictly for SQL Server and supports all its features. the OleDb.NET provider is a general provider and can be used for connectivity to any database Sql Server, Access, Oracel, etc... Similarly you should use the Oracle.NET dataprovider for connecting to oracle. There are finer points than what I've mentioned but that the bird's eye view.

        W Offline
        W Offline
        wayward
        wrote on last edited by
        #3

        ... except the SQL Server .NET data provider doesn't support COMPUTE BY clauses ... James.

        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