Moving from JDBC to ADO.NET

One of our customers who wanted to move from JDBC to ADO.NET wrote to us that he was unable to find any article, white pages or case studies about migration database applications from java to .NET i.e. JDBC to ADO.net. He wanted help in finding the relevant information.

A> Data access technologies have been continuously evolving. At first, database vendors released proprietary C libraries that bound applications natively to their database management system. Since then, Microsoft® has released numerous data access tools: ODBC, DAO, OLE DB, RDO and ADO to name a few. ODBC was the first widely accepted technology to harness the flexibility of generic database programming. OLE DB and ADO were built to supply data access tools to the world of COM programmers. Microsoft ADO.NET, the most recent evolution in this family of technology, integrates relational database access into the Microsoft .NET environment.

On the Java side, JDBC was modeled after the success of ODBC. The idea was to define generic data access interfaces for developers; independent vendors would then provide competing implementations of these interfaces. Developers would then be free to plug-in whatever implementation suited their application best.

This article will first give a brief review of database access in Java. It will then discuss the changes the Java Language Conversion Assistant (JLCA) will make to database-accessing code during the conversion process, and the changes you will need to make to this code. Finally, it will provide an overview of the various ways to interact with a database using ADO.NET…

Read more about this at … https://msdn.microsoft.com/asp.net/using/migrating/jspmig/phase1/default.aspx?pull=/library/en-us/dnaspp/html/ASPNet-JSPMig-AdoNet.asp