@prefix rdf: . @prefix ns1: . @prefix foaf: . ns1:this rdf:type foaf:Person . @prefix atom: . rdf:type atom:Feed . @prefix sioct: . rdf:type sioct:Weblog . @prefix rdfs: . rdfs:label "kidehen@openlinksw.com's BLOG [127] description" . rdf:type atom:Entry , sioct:BlogPost . @prefix dc: . dc:title "Microsoft Data Access API Backgrounder: ODBC " ; foaf:maker ns1:this ; rdfs:label "Microsoft Data Access API Backgrounder: ODBC " . @prefix dt: . @prefix dcterms: . dcterms:created "2007-01-03T18:20:45Z"^^dt:dateTime ; dcterms:modified "2007-01-03T13:35:51.000001-05:00"^^dt:dateTime . @prefix sioc: . sioc:id "4d8b82441fd49d14802aae0eb9e4510b" ; sioc:link ; sioc:content "Mike Pizzo has commenced a much needed 4-part article series covering the history of Microsoft's various Data Access related APIs. Naturally, Part 1 covers: Open Database Connectivity (ODBC) which is the first of a series of purpose specific Data Access APIs.\n\nHere is a very important excerpt:\n\n\n...\nAnd then something happened. Visual Basic became popular as a scriptable "automation language". ODBC, being a C-style interface, was not directly consumable from VB. However, some of you clever folks figured out that Microsoft Access supported executing queries against ODBC Datasources, and that Access did support scriptable automation through its Data Access Object (DAO) API. Voila! Now you could write applications against ODBC sources using VB.\n\nHowever, DAO went through Access's internal "Jet" (Joint Engine Technology) database engine, which defaulted to building local keysets for each result in order to do advanced query processing and cursoring against the remote data. This was fine if you needed that functionality, but significant performance overhead and additional round trips when you didn't.\n\nEnter the Visual Basic team who, responding to customer demand for better performance against ODBC sources, came up with something called Remote Data Objects (RDO). RDO implemented the same DAO programming patterns directly against ODBC, rather than going through Jet. RDO was extremely popular among VB developers, but the fact that we had two different sets of automation objects for accessing ODBC sources caused confusion.\n\nBut apparently not enough confusion, because our solution was to introduce "ODBCDirect". Despite its name, ODBCDirect was not a new API; it was just a mode we added to DAO that set defaults in such a way as to avoid the overhead of building keysets and such\n...\n\n\n\nTo this very day (unfortunately!) ODBC has been maligned by the perpetuated misunderstanding of JET's DAO layer that sits atop ODBC providing advanced query processing (i.e. Virtual DBMS functionality) alongside a client-side keyset cursor model implementation." ; atom:title "Microsoft Data Access API Backgrounder: ODBC " . @prefix ns10: . sioc:has_creator ns10:this ; sioc:has_container ; sioc:links_to . @prefix ns11: . sioc:links_to ns11:Open_Database_Connectivity ; atom:source ; atom:author ns1:this ; atom:published "2007-01-03T18:20:45Z" ; atom:updated "2007-01-03T18:35:51Z" . @prefix opl: . opl:isDescribedUsing . ns10:this rdf:type sioc:User . @prefix rdf: . @prefix ns1: . @prefix foaf: . ns1:this rdf:type foaf:Person ; foaf:made . @prefix atom: . rdf:type atom:Feed . @prefix sioct: . rdf:type sioct:Weblog . @prefix rdfs: . rdfs:label "kidehen@openlinksw.com's BLOG [127] description" . @prefix sioc: . sioc:container_of ; atom:entry ; atom:contains . @prefix ns7: . ns7:this rdf:type sioc:User ; sioc:creator_of .