ODBC applications have the power to access data in a lot of leading database management systems (DBMS) through the use of ODBC drivers that have encrypted access. To run ODBC applications it is imperative that programmers get familiar with both ODBC programming and managing SQL Server.
In architecture, Microsoft SQL Server ODBC driver has to employ the components of standard SQL Server needed in the communication process between the client application and the database server. The ODBC driver can disregard the older versions of the SQL Server because the ODBS driver can directly write data to the same Net-Library layer that is employed by the DB Library.
The ODBC driver manager which looks like a very slim layer is able to manage communications that take place between the working application per se and the ODBC drivers. ODBC driver manager specifically loads the available modules found in the drivers and then delivers all the ODBC requests to the driver.
The SQL Server ODBC driver is the single DLL (Dynamic Link Library) that replies to all calls made by the applications to the ODBC application programming interface. It can also do data translation, wherein the statements that came from applications that contain syntax not supported by SQL Server into Transact-SQL syntax which in turn gets passed to the server.
The SQL Server Client Network Library allows the communications that take place in the driver via the SQL Net-Libraries Server and the Tabular Data Stream. The protocol for SQL Server TDS is in fact a half-duplex procedure that contains self-sufficient result sets. Such results are optimized with an access to the database.
The ODBC driver manager, SQL Server ODBC driver, and the SQL Server Client Network Library are just some of the components in the architecture of Microsoft SQL Server that employs ODBC.