1. Hana Driver Odbc Postgresql

• Mar 10, 2017. SQL ODBC driver 3. Universal Data Access Components (ODAC) is a powerful tool for developing cross- database client/server applications in Delphi, C++Builder, Lazarus (and Free Pascal) under Windows, Mac OS X, i. OS, Android, Linux, and Free. BSD for both 3. 2- bit and 6.
• If you are a new customer, register now for access to product evaluations and purchasing capabilities. Need access to an account? If your company has an.

Download operating system-specific drivers for Windows and Linux that allow you to connect to a wide range of data sources.

To connect to an SAP HANA database from ArcGIS clients, install and configure the SAP HANA client ODBC driver on the ArcGIS client machines. SAP HANA client ODBC drivers are available to existing SAP users from the SAP Support Portal under Software Downloads.

Once the ODBC driver is configured on all your ArcGIS client machines, create a database connection file. To publish ArcGIS Server web services that reference the data in your SAP HANA database, register the database connection file with your ArcGIS Server sites.

Note:

Install 32- and 64-bit applications and ODBC drivers on separate machines to avoid issues that arise when different versions of the same drivers are installed on the same machine.

Connect from ArcMap

To connect from ArcMap to SAP HANA, install and configure the SAP HANA client ODBC driver on all ArcMap machines and create a connection from ArcMap to the database.

Install the SAP HANA client ODBC driver

Follow these steps to download the SAP HANA client ODBC driver and configure the path variable on your client machine:

1. Download a supported 32-bit SAP HANA clientfrom the SAP Support Portal, and install it on each ArcMap machine.
2. Add the SAP HANA client installation directory to the Microsoft Windows system PATH environment variable.

   For example, if you installed the SAP HANA client ODBC driver to C:Program Filessaphdbclient, add that to the PATH environment variable.

Connect to the database

You can use the SAP HANA server name and the SQL port number to connect to the database if all of the following are true for your site:

• Your SAP HANA database is a supported release, 2.0 SPS2 or later.
• You're connecting from ArcGIS Desktop 10.6.1 or a later release.
• The number of characters in the SAP HANA server name and SQL port number of your SAP HANA server is fewer than 31.

If any of the above conditions are not met, you must configure a system data source name (DSN) for the SAP HANA client ODBC driver before you can proceed with the following steps to connect from ArcMap.

Add a database connection using the Database Connection dialog box or the Create Database Connection geoprocessing tool. The following steps describe using the Database Connection dialog box:

1. Expand Database Connections in the Catalog tree in ArcMap or ArcCatalog and double-click Add Database Connection.
2. Choose SAP HANA from the Database Platform drop-down list.
3. In the Data source text box, type one of the following:
   • The SAP HANA server name and the SQL port number used to communicate with the database separated by a colon (:). For example, if the fully qualified name of your SAP HANA server is myserver.network.com and SAP HANA communicates through port 98765, type myserver.network.com:98765.
   • The data source name you configured for the ODBC driver.
4. Choose Database authentication for the Authentication Type.
5. Provide a valid user name and password in the User name and Password text boxes, respectively.
6. If you prefer not to save your login information as part of the connection, uncheck Save user name and password; doing this can help maintain the security of the database. However, if you do this, you will be prompted to provide a user name and password every time you connect from desktop clients.

   Note:

   Save user name and password must be checked for connection files that you register with an ArcGIS Server site or if you want to use the Catalog search to locate data accessed through this connection file.

7. Click OK to connect.

A file is created in <computer_name>Users<user_name>AppDataRoamingESRIDesktop<release#>ArcCatalog.

You can move the connection to another location; just be sure users and applications that need to make a connection have read access to the directory where you place the connection file.

If you use the data from this connection as the source for a service, such as a geoprocessing or geocoding service, you may need to place the connection file in a shared location on your network. See Make your data accessible to ArcGIS Server for more information about sharing a connection file.

Configure a data source name (optional in most cases)

If any of the following conditions are true, you must configure a system data source name (DSN) for the SAP HANA client ODBC driver to connect to the database:

• You're using SAP HANA 1.0 (any supported service pack release).
• You're connecting from ArcGIS Desktop 10.6 or an earlier release.
• The number of characters in the SAP HANA server name and SQL port number of your SAP HANA server exceeds 31.

If these conditions do not exist at your site, you can still configure a data source name to connect to SAP HANA, but it is not required.

Follow these steps to configure a data source name for your SAP HANA database:

RG Mechanics, Free Download, full pc game, pc game, RG Mechanics Website, Website For RePack, RePack PC Games, Download All Cracked, Cracked, youwatch serie, Highly Compressed, PC Games, Games For Free, For Free, Direct Download, Download, Download Links, Links PC Games, RG Mechanics Links, RG Mechanics illimit, Nosteam full pc game, RELOADED, CPY, CODEX, Netflix streaming, Full Installer, Online, Server List, google, youtube, repack, SKIDROW, COREPACK,Full-Game, Requested ISO,ISO Crcak,skidrowreloaded,thepiratebay,Kickass Torrents: KAT,KAT,Best Download RG Mechanics WEBSITE. Dead island highly compressed pc game free download.

1. Open the ODBC Data Source Administrator (32 bit) on your client machine.

   Note:

   Use the same name when configuring all SAP HANA ODBC clients to that same database. For example, use the same data source name when you configure the SAP HANA client ODBC driver on your ArcMap machines as you use when you configure the data source name for the ODBC driver on your ArcGIS Server machines. If you do not use the same name, you will encounter problems when publishing, because ArcGIS compares the connection strings of the data being published and the database that is registered.

2. Click the System DSN tab in the ODBC Data Source Administrator (64 bit) and click Add.
3. Choose the SAP HANA ODBC client and click Finish.
4. Provide a name, description, and SQL port number for the data source.
5. Click OK on the ODBC client setup and ODBC Data Source Administrator to close them.

Connect from ArcGIS Server

If you want to publish SAP HANA data to an ArcGIS Server site and want the resultant services to use the data in SAP HANA, install a 64-bit SAP HANA client ODBC driver on each machine in the ArcGIS Server site. Follow the instructions specific to the operating system where ArcGIS Server is installed.

Once you've configured the machines in the ArcGIS Server site, create a database connection to your database and register the connection file with your ArcGIS Server site.

Install the SAP HANA on the ArcGIS Server machines (Microsoft Windows)

Download the SAP HANA client ODBC driver and install it on each machine in the ArcGIS Server site.

Install the SAP HANA client ODBC driver on each ArcGIS ServerWindows machine:

1. Download a supported 64-bit SAP HANA client from the SAP Support Portal, and install it on each machine in the ArcGIS Server site.
2. Add the SAP HANA client installation directory to the Windows system PATH environment variable.

   For example, if you installed the SAP HANA client ODBC driver to C:Program Filessaphdbclient, add that to the PATH environment variable.

Once you have the SAP HANA client ODBC driver installed, you can proceed with registering a database connection with your ArcGIS Server site. If the following conditions exist, however, you must configure a data source name for the ODBC driver before you register a database connection.

• You're using SAP HANA 1.0 (any supported service pack release).
• You're connecting to the database from ArcGIS Server 10.6 or an earlier release.
• The number of characters in the SAP HANA server name and SQL port number of your SAP HANA server exceeds 31.

Configure an ODBC data source name on Windows (optional in most cases)

If you require a data source name, follow these steps to configure a system data source name (DSN) for the SAP HANA client ODBC driver on each ArcGIS ServerWindows machine:

Note:

Use the data source name when you connect from ArcGIS to the database. Use the same name when configuring all SAP HANA ODBC clients to that same database. For example, use the same data source name when you configure the SAP HANA client ODBC driver on your ArcGIS Pro and ArcMap machines as you use when you configure the data source name for the ODBC driver on your ArcGIS Server machines. If you do not use the same name, you will encounter problems when publishing, because ArcGIS compares the connection strings of the data being published and the database that is registered.

1. Open the ODBC Data Source Administrator (64 bit).
2. Click the System DSN tab in the ODBC Data Source Administrator (64 bit) and click Add.
3. Choose the SAP HANA ODBC client and click Finish.
4. Populate the Data Source Name, Description, and Server:Port information for your database.
5. Click Settings to open the ODBC Advanced Setup dialog box and add the following key value to the Special property settings section: SPATIALTYPES=1. Click OK to apply the changes and close the ODBC Advanced Setup dialog box.

   Note:

   You can skip this step if you are using ArcGIS Server with a supported version of SAP HANA 2.0 or later.

6. Click OK on the ODBC client setup and ODBC Data Source Administrator to close them.

Install the SAP HANA on the ArcGIS Server machines (Linux)

Download the SAP HANA client ODBC driver. Place the client on each machine in the ArcGIS Server site, install it, and edit the ArcGIS Serverinit_user_param.sh script on each ArcGIS ServerLinux machine.

1. Download a supported 64-bit SAP HANA client from the SAP Support Portal, and install it on each machine in the ArcGIS Server site.
2. Install a Linux ODBC driver manager on each ArcGIS Server machine if one is not already installed.

Once you have installed the database client files, alter the init_user_param.sh script installed with ArcGIS Server to reference the client files. You can access this script by browsing to the <ArcGIS Server installation directory>/arcgis/server/usr directory.

3. Ensure that the ArcGIS Server installation owner on each machine has at least read and execute permissions on the database client libraries.
4. Open the init_user_param.sh script in a text editor.
5. Remove the comment mark (#) from these lines and replace the <SAPHANA_InstallDir> information with the path to the directory where you installed the SAP HANA client:
6. Save and close the script.
7. After you have configured the init_user_param.sh on each machine in your ArcGIS Server site, run the startserver.sh script on each machine to restart ArcGIS Server.

   ./startserver.sh

Once you have the SAP HANA client ODBC driver installed, you can proceed with registering a database connection with your ArcGIS Server site. If the following conditions exist, however, you must configure a data source name for the ODBC driver before you register a database connection.

Hana Driver Odbc Postgresql

• You're using SAP HANA 1.0 (any supported service pack release).
• You're connecting to the database from ArcGIS Server 10.6 or an earlier release.
• The number of characters in the SAP HANA server name and SQL port number of your SAP HANA server exceeds 31.

Configure an ODBC data source name on Linux (optional in most cases)

If you require a data source name, follow these steps to configure a system data source name for the SAP HANA client ODBC driver on each ArcGIS ServerLinux machine:

Note:

Use the same ODBC data source name when configuring all SAP HANA ODBC clients to that same database. For example, configure the data source name on your ArcGIS Pro and ArcMap machines to be the same as the data source name for the SAP HANA client ODBC driver on the machines in your ArcGIS Server sites. If you do not use the same name, you will encounter problems when publishing, because ArcGIS compares the connection strings of the data being published and the database that is registered.

1. To configure an ODBC data source name, edit the SAP HANA ODBC connection files, .odbc.ini and .odbcinst.ini.

   The files must be named .odbc.ini and .odbcinst.ini.

2. Open the .odbc.ini file in a text editor.

   Be sure there are no spaces around the equal signs (=) in the .odbc.ini file. For example, this entry does not have spaces around the equal signs:

   Note:

   The SPATIALTYPES=1 entry is not required if you are using ArcGIS Server with a supported version of SAP HANA 2.0 or a later release.

3. Save and close the .odbc.ini file.
4. Open the .odbcinst.ini file and edit it to include the ODBC driver path.

   In the .odbcinst.ini file, the same sort of spacing is not required, as shown in this example:

5. Save and close the .odbcinst.ini file.

Register the database

If you want to publish web services using data in SAP HANA, create a database connection and register it with your ArcGIS Server sites. You can connect to an SAP HANA from ArcMap or ArcGIS Server Manager. You cannot connect to a geodatabase in SAP HANA from ArcMap.

In computing, Open Database Connectivity (ODBC) is a standard application programming interface (API) for accessing database management systems (DBMS). The designers of ODBC aimed to make it independent of database systems and operating systems. An application written using ODBC can be ported to other platforms, both on the client and server side, with few changes to the data access code.

ODBC accomplishes DBMS independence by using an ODBC driver as a translation layer between the application and the DBMS. The application uses ODBC functions through an ODBC driver manager with which it is linked, and the driver passes the query to the DBMS. An ODBC driver can be thought of as analogous to a printer driver or other driver, providing a standard set of functions for the application to use, and implementing DBMS-specific functionality. An application that can use ODBC is referred to as 'ODBC-compliant'. Any ODBC-compliant application can access any DBMS for which a driver is installed. Drivers exist for all major DBMSs, many other data sources like address book systems and Microsoft Excel, and even for text or comma-separated values (CSV) files.

ODBC was originally developed by Microsoft and Simba Technologies during the early 1990s, and became the basis for the Call Level Interface (CLI) standardized by SQL Access Group in the Unix and mainframe field. ODBC retained several features that were removed as part of the CLI effort. Full ODBC was later ported back to those platforms, and became a de facto standard considerably better known than CLI. The CLI remains similar to ODBC, and applications can be ported from one platform to the other with few changes.

• 1History
• 2Drivers and Managers
• 3Bridging configurations

History[edit]

Before ODBC[edit]

The introduction of the mainframe-based relational database during the 1970s led to a proliferation of data access methods. Generally these systems operated together with a simple command processor that allowed users to type in English-like commands, and receive output. The best-known examples are SQL from IBM and QUEL from the Ingres project. These systems may or may not allow other applications to access the data directly, and those that did use a wide variety of methodologies. The introduction of SQL aimed to solve the problem of language standardization, although substantial differences in implementation remained.

Also, since the SQL language had only rudimentary programming features, users often wanted to use SQL within a program written in another language, say Fortran or C. This led to the concept of Embedded SQL, which allowed SQL code to be embedded within another language. For instance, a SQL statement like SELECT * FROM city could be inserted as text within C source code, and during compiling it would be converted into a custom format that directly called a function within a library that would pass the statement into the SQL system. Results returned from the statements would be interpreted back into C data formats like char * using similar library code.

There were several problems with the Embedded SQL approach. Like the different varieties of SQL, the Embedded SQLs that used them varied widely, not only from platform to platform, but even across languages on one platform – a system that allowed calls into IBM's DB2 would look very different from one that called into their own SQL/DS.^[dubious] Another key problem to the Embedded SQL concept was that the SQL code could only be changed in the program's source code, so that even small changes to the query required considerable programmer effort to modify. The SQL market referred to this as static SQL, versus dynamic SQL which could be changed at any time, like the command-line interfaces that shipped with almost all SQL systems, or a programming interface that left the SQL as plain text until it was called. Dynamic SQL systems became a major focus for SQL vendors during the 1980s.

Older mainframe databases, and the newer microcomputer based systems that were based on them, generally did not have a SQL-like command processor between the user and the database engine. Instead, the data was accessed directly by the program – a programming library in the case of large mainframe systems, or a command line interface or interactive forms system in the case of dBASE and similar applications. Data from dBASE could not generally be accessed directly by other programs running on the machine. Those programs may be given a way to access this data, often through libraries, but it would not work with any other database engine, or even different databases in the same engine. In effect, all such systems were static, which presented considerable problems.

Early efforts[edit]

By the mid-1980s the rapid improvement in microcomputers, and especially the introduction of the graphical user interface and, MS, Tandem, DEC and Sybase, brought an updated version of SQLC to the next SAG meeting in June 1990.^[7] The SAG responded by opening the standard effort to any competing design, but of the many proposals, only Oracle Corp had a system that presented serious competition. In the end, SQLC won the votes and became the draft standard, but only after large portions of the API were removed – the standards document was trimmed from 120 pages to 50 during this time. It was also during this period that the name Call Level Interface was formally adopted.^[7] In 1995 SQL/CLI became part of the international SQL standard, ISO/IEC 9075-3.^[8] The SAG itself was taken over by the X/Open group in 1996, and, over time, became part of The Open Group's Common Application Environment.

MS continued working with the original SQLC standard, retaining many of the advanced features that were removed from the CLI version. These included features like scrollable cursors, and metadata information queries. The commands in the API were split into groups; the Core group was identical to the CLI, the Level 1 extensions were commands that would be easy to implement in drivers, while Level 2 commands contained the more advanced features like cursors. A proposed standard was released in December 1991, and industry input was gathered and worked into the system through 1992, resulting in yet another name change to ODBC.^[9]

JET and ODBC[edit]

During this time, Microsoft was in the midst of developing their Jet database system. Jet combined three primary subsystems; an ISAM-based database engine (also named Jet, confusingly), a C-based interface allowing applications to access that data, and a selection of driver dynamic-link libraries (DLL) that allowed the same C interface to redirect input and output to other ISAM-based databases, like Paradox and xBase. Jet allowed using one set of calls to access common microcomputer databases in a fashion similar to Blueprint, by then renamed DataLens. However, Jet did not use SQL; like DataLens, the interface was in C and consisted of data structures and function calls.

The SAG standardization efforts presented an opportunity for Microsoft to adapt their Jet system to the new CLI standard. This would not only make Windows a premier platform for CLI development, but also allow users to use SQL to access both Jet and other databases as well. What was missing was the SQL parser that could convert those calls from their text form into the C-interface used in Jet. To solve this, MS partnered with PageAhead Software to use their existing query processor, SIMBA. SIMBA was used as a parser above Jet's C library, turning Jet into an SQL database. And because Jet could forward those C-based calls to other databases, this also allowed SIMBA to query other systems. Microsoft included drivers for Excel to turn its spreadsheet documents into SQL-accessible database tables.^[10]

Release and continued development[edit]

ODBC 1.0 was released in September 1992.^[11] At the time, there was little direct support for SQL databases (versus ISAM), and early drivers were noted for poor performance. Some of this was unavoidable due to the path that the calls took through the Jet-based stack; ODBC calls to SQL databases were first converted from Simba Technologies's SQL dialect to Jet's internal C-based format, then passed to a driver for conversion back into SQL calls for the database. Digital Equipment and Oracle both contracted Simba Technologies to develop drivers for their databases as well.^[12]

Circa 1993, OpenLink Software shipped one of the first independently developed third-party ODBC drivers, for the PROGRESS DBMS,^[13] and soon followed with their UDBC (a cross-platform API equivalent of ODBC and the SAG/CLI) SDK and associated drivers for PROGRESS, Sybase, Oracle, and other DBMS, for use on Unix-like OS (AIX, HP-UX, Solaris, Linux, etc.), VMS, Windows NT, OS/2, and other OS.^[14]

Meanwhile, the CLI standard effort dragged on, and it was not until March 1995 that the definitive version was finalized. By then, Microsoft had already granted Visigenic Software a source code license to develop ODBC on non-Windows platforms. Visigenic ported ODBC to a wide variety of Unix platforms, where ODBC quickly became the de facto standard.^[15] 'Real' CLI is rare today. The two systems remain similar, and many applications can be ported from ODBC to CLI with few or no changes.^[16]

Over time, database vendors took over the driver interfaces and provided direct links to their products. Skipping the intermediate conversions to and from Jet or similar wrappers often resulted in higher performance. However, by then Microsoft had changed focus to their OLE DB^[17] concept (recently reinstated ^[18]), which provided direct access to a wider variety of data sources from address books to text files. Several new systems followed which further turned their attention from ODBC, including ActiveX Data Objects (ADO) and ADO.net, which interacted more or less with ODBC over their lifetimes.

As Microsoft turned its attention away from working directly on ODBC, the Unix field was increasingly embracing it. This was propelled by two changes within the market, the introduction of graphical user interfaces (GUIs) like GNOME that provided a need to access these sources in non-text form, and the emergence of open software database systems like PostgreSQL and MySQL, initially under Unix. The later adoption of ODBC by Apple for using the standard Unix-side iODBC package Mac OS X 10.2 (Jaguar)^[19] (which OpenLink Software had been independently providing for Mac OS X 10.0 and even Mac OS 9 since 2001^[20]) further cemented ODBC as the standard for cross-platform data access.

Sun Microsystems used the ODBC system as the basis for their own open standard, Java Database Connectivity (JDBC). In most ways, JDBC can be considered a version of ODBC for the programming language Java instead of C. JDBC-to-ODBC bridges allow Java-based programs to access data sources through ODBC drivers on platforms lacking a native JDBC driver, although these are now relatively rare. Inversely, ODBC-to-JDBC bridges allow C-based programs to access data sources through JDBC drivers on platforms or from databases lacking suitable ODBC drivers.

ODBC today[edit]

ODBC remains in wide use today, with drivers available for most platforms and most databases. It is not uncommon to find ODBC drivers for database engines that are meant to be embedded, like SQLite, as a way to allow existing tools to act as front-ends to these engines for testing and debugging.^[21]

However, the rise of thin client computing using HTML as an intermediate format has reduced the need for ODBC. Many web development platforms contain direct links to target databases – MySQL being very common. In these scenarios, there is no direct client-side access nor multiple client software systems to support; everything goes through the programmer-supplied HTML application. The virtualization that ODBC offers is no longer a strong requirement, and development of ODBC is no longer as active as it once was.^{[citation needed]}

Version history[edit]

Version history:^[22]

• 1.0: released in September 1992^[23]
• 2.0: c. 1994
• 2.5
• 3.0: c. 1995, John Goodson of Intersolv and Frank Pellow and Paul Cotton of IBM provided significant input to ODBC 3.0^[24]
• 3.5: c. 1997
• 3.8: c. 2009, with Windows 7^[25]
• 4.0: Development announced June 2016^[26] with draft spec on Github

Drivers and Managers[edit]

Drivers[edit]

ODBC is based on the device driver model, where the driver encapsulates the logic needed to convert a standard set of commands and functions into the specific calls required by the underlying system. For instance, a printer driver presents a standard set of printing commands, the API, to applications using the printing system. Calls made to those APIs are converted by the driver into the format used by the actual hardware, say PostScript or PCL.

In the case of ODBC, the drivers encapsulate many functions that can be broken down into several broad categories. One set of functions is primarily concerned with finding, connecting to and disconnecting from the DBMS that driver talks to. A second set is used to send SQL commands from the ODBC system to the DBMS, converting or interpreting any commands that are not supported internally. For instance, a DBMS that does not support cursors can emulate this functionality in the driver. Finally, another set of commands, mostly used internally, is used to convert data from the DBMS's internal formats to a set of standardized ODBC formats, which are based on the C language formats.

An ODBC driver enables an ODBC-compliant application to use a data source, normally a DBMS. Some non-DBMS drivers exist, for such data sources as CSV files, by implementing a small DBMS inside the driver itself. ODBC drivers exist for most DBMSs, including Oracle, PostgreSQL, MySQL, Microsoft SQL Server (but not for the Compact aka CE edition), Sybase ASE, SAP HANA^[27][28] and DB2. Because different technologies have different capabilities, most ODBC drivers do not implement all functionality defined in the ODBC standard. Some drivers offer extra functionality not defined by the standard.

Driver Manager[edit]

Device drivers are normally enumerated, set up and managed by a separate Manager layer, which may provide additional functionality. For instance, printing systems often include functionality to provide spooling functionality on top of the drivers, providing print spooling for any supported printer.

In ODBC the Driver Manager (DM) provides these features.^[29] The DM can enumerate the installed drivers and present this as a list, often in a GUI-based form.

But more important to the operation of the ODBC system is the DM's concept of a Data Source Name (DSN). DSNs collect additional information needed to connect to a specific data source, versus the DBMS itself. For instance, the same MySQL driver can be used to connect to any MySQL server, but the connection information to connect to a local private server is different from the information needed to connect to an internet-hosted public server. The DSN stores this information in a standardized format, and the DM provides this to the driver during connection requests. The DM also includes functionality to present a list of DSNs using human readable names, and to select them at run-time to connect to different resources.

The DM also includes the ability to save partially complete DSN's, with code and logic to ask the user for any missing information at runtime. For instance, a DSN can be created without a required password. When an ODBC application attempts to connect to the DBMS using this DSN, the system will pause and ask the user to provide the password before continuing. This frees the application developer from having to create this sort of code, as well as having to know which questions to ask. All of this is included in the driver and the DSNs.

Bridging configurations[edit]

A bridge is a special kind of driver: a driver that uses another driver-based technology.

ODBC-to-JDBC (ODBC-JDBC) bridges[edit]

An ODBC-JDBC bridge consists of an ODBC driver which uses the services of a JDBC driver to connect to a database. This driver translates ODBC function-calls into JDBC method-calls. Programmers usually use such a bridge when they lack an ODBC driver for some database but have access to a JDBC driver. Examples: OpenLink ODBC-JDBC Bridge, SequeLink ODBC-JDBC Bridge.

JDBC-to-ODBC (JDBC-ODBC) bridges[edit]

A JDBC-ODBC bridge consists of a JDBC driver which employs an ODBC driver to connect to a target database. This driver translates JDBC method calls into ODBC function calls. Programmers usually use such a bridge when a given database lacks a JDBC driver, but is accessible through an ODBC driver. Sun Microsystems included one such bridge in the JVM, but viewed it as a stop-gap measure while few JDBC drivers existed (The built-in JDBC-ODBC bridge was dropped from the JVM in Java 8^[30]). Sun never intended its bridge for production environments, and generally recommended against its use. As of 2008 independentmw-data:TemplateStyles:r886058088'>

External links[edit]

• Microsoft ODBC & Data Access APIs History Article.