Powered by Zoomin Software. For more details please contactZoomin

DataDirect Connect for ADO.NET Data Provider Installation Guide

System and Product Requirements

  • Last Updated: April 5, 2026
  • 6 minute read
    • ADO.NET
    • Documentation

For hard disk space requirements, refer to the product README text file.

Installing the data providers requires .NET Framework 4.6 or higher.

The DataDirect Connect ADO.NET Entity Framework data providers are supported on the ADO.NET Entity Framework supplied in the Microsoft .NET Framework Versions 3.5 SP1, 4.5.2, 4.6.x and 4.7. The data provider is compatible with Visual Studio 2015 and Visual Studio 2017.

Supported Operating Environments

The following table lists the supported operating environments for the data providers.

Note: Refer to driver-specific support matrix for Entity Framework Support

Operating Environments Supported

Operating Environment .NET Framework Version
3.5 SP1 4.5.2 4.6.x 4.7
32-bit Operating Systems (x86)        
Windows 10 (all Editions) x x x x
Windows Server 2016 (all Editions) x x x x
Windows 8 (all Editions) x x x x
Windows Server 2012 (all Editions) x x x x
Windows 7 (all Editions) x x x x
Windows Server 2008 (all Editions)1 x x x x
Windows Vista (all Editions) x x x x
Windows Server 2003 (all Editions) x x x x
64-bit Operating Systems (x64) AMD Opteron and Intel Xeon with Extended Memory 64 Technology (EM64T)
Windows 10 (all Editions) x x x x
Windows Server 2016 (all Editions) x x x x
Windows 8 (all Editions) x x x x
Windows Server 2012 (all Editions) x x x x
Windows 7 (all Editions) x x x x
Windows Server 2008 (all Editions) x x x x
Windows Vista (all Editions) x x x x
Windows Server 2003 x x x x
Virtualized Environments
VMWare VI Enterprise x x x x
Windows Server 2008 Hyper-V x x x x

1 Includes HPC Server 2008 and Web Server 2008.

Existing code written for earlier versions of the .NET Framework and earlier versions of DataDirect Connect for .NET is compatible with the 4.3 version of the data providers. Note that the applications built using .NET 1.1 or applications built with .NET 2.0 and directly referencing DataDirect provider assemblies must be recompiled. If recompiling is not an option, then you can use .NET facilities to redirect references to the older assemblies to the newer assemblies.

Development Environment

If you purchased a Developer’s license, you must install the data provider on a development machine that has Microsoft Visual Studio installed. Developer’s licenses cannot be used in a production environment.

The following versions of Microsoft Visual Studio are supported:

  • Visual Studio 2017
  • Visual Studio 2015

Note: The Developer’s license for the DataDirect Connect for ADO.NET data providers is designed for use with Microsoft Visual Studio. If you create .NET applications with another .NET development tool, contact your sales representative for the appropriate license.

ADO.NET Entity Framework

The DataDirect Connect ADO.NET Entity Framework data providers have the following requirements:

  • .NET Framework Version 3.5 Service Pack 1, 4.5.2 or higher
  • Visual Studio 2015 and/or Visual Studio 2017
  • Visual C++ Redistributable for Visual Studio 2012 Update 4. Note that you must install the 32-bit redistributable package on a 32-bit machine, and install both 32-bit and 64-bit redistributable packages on a 64-bit machine. This is becasue the 64-bit machine can host both 32bit and 64bit applications.
  • One of the following data stores:
    • Oracle 9.2.0.4 or higher
    • DB2 UDB V7R1, V7R2 and V7R3 and V6R1 for iSeries
    • SAP ASE 15.0.x, 15.5, 15.7, 15.9 and 16

DataDirect Connect for ADO.NET Entity Framework data providers can be used with applications that use the standard ADO.NET features or with the ADO.NET Entity Framework.

  • The DB2 and Oracle ADO.NET Entity Framework data provider can be used with applications that use the features of the standard .NET Framework 4.0 or higher and the ADO.NET Entity Framework 4.1, 4.2, 4.3, 5.0 or 6.0. To use Plain Old CLR Objects (POCO) entities or Model First, you must use .NET Framework 4.0 or higher. To use Code First, you must use ADO.NET Entity Framework 4.1, 4.2, 4.3, or 5.0. To use Code First Migrations, you must use ADO.NET Entity Framework 4.3 or higher. To use Table Valued Functions and Enumerated Type features, you must use ADO.NET Entity Framework 5.0 and higher.
  • The SAP ASE ADO.NET Entity Framework data providers can be used with applications that use the features of the standard .NET Framework 3.5 SP1, including ADO.NET Entity Framework funcionality. This means that these data providers support the Database First approach. To use Plain Old CLR Objects (POCO) entities, you must use .NET Framework 4.0 or higher.

Using Distributed Transactions

The DataDirect Connect for ADO.NET data providers support distributed transactions using the Microsoft Distributed Transaction Coordinator (MS DTC). The MS DTC is provided through System.Transaction.

Kerberos Authentication

Kerberos authentication is a trusted third-party authentication service. Kerberos authentication can take advantage of the user name and password maintained by the operating system to authenticate users to the database or use another set of user credentials specified by the application.

The DataDirect Connect for ADO.NET data providers support Kerberos authentication.

Verify that your environment meets the requirements listed in the following table before you configure your data provider for Kerberos authentication.

Kerberos Authentication Requirements for the Data Providers

Component Requirements
Database server The database server must be running one of the following databases:
DB2:
  • DB2 11.1 for Linux/UNIX/Windows
  • DB2 10.1 for Linux/UNIX/Windows
  • DB2 V9.1, V9.5, V9.7 for Linux/UNIX/Windows
  • DB2 V8.1 for Linux/UNIX/Windows
  • DB2 for z/OS V8.1 till DB2 for z/OS 12
  • DB2 V5R4 till V7R3

Oracle:
  • Oracle 12c (R1 and R2)
  • Oracle 11g (R1 and R2)
  • Oracle 10g (R1 and R2)
  • Oracle 9i (R2)

Microsoft SQL Server:
  • Microsoft SQL Server 2017
  • Microsoft SQL Server 2016
  • Microsoft SQL Server 2014
  • Microsoft SQL Server 2008
  • Microsoft SQL Server 2005
  • Microsoft SQL Server 2000
  • Microsoft SQL Server 2000 Enterprise Edition

SAP ASE/ Sybase:
  • SAP ASE 12.0 or higher
Kerberos server The Kerberos server is the machine where the user IDs for authentication are administered. The Kerberos server is also the location of the Kerberos Key Distribution Center (KDC). If using Windows Active Directory, this machine is also the domain controller.
DB2, Oracle, and SAP ASE:
Network authentication must be provided by one of the following methods:
  • Windows Active Directory on one of the following operating systems:
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows Vista
    • Windows Server 2016
    • Windows Server 2012
    • Windows Server 2008
    • Windows Server 2003
  • MIT Kerberos 1.4.2 or higher
Microsoft SQL Server: Network authentication must be provided by Windows Active Directory on one of the following operating systems:
  • Windows 10
  • Windows Server 2016
  • Windows 8
  • Windows Server 2012
  • Windows 7
  • Windows Server 2008
  • Windows Server 2003

To use Kerberos authentication, some configuration is required after installation of DataDirect Connect for ADO.NET. Refer to the DataDirect Connect Series for ADO.NET Help for more information.

NTLM Authentication

NTLM authentication is a single sign-on OS authentication method. This method provides authentication from Windows clients only and requires minimal configuration.

The DataDirect Connect for ADO.NET SQL Server and Oracle data providers support NTLM authentication.

Verify that your environment meets the requirements listed in the following table before you configure the data provider for NTLM authentication.

NTLM Authentication Requirements for the Data Providers

Component Requirements
Database server The database server must be administered by the same domain controller that administers the client and must be running one of the following databases:
  • Microsoft SQL Server 2017
  • Microsoft SQL Server 2016
  • Microsoft SQL Server 2014
  • Microsoft SQL Server 2012
  • Microsoft SQL Server 2008
  • Microsoft SQL Server 2005
  • Microsoft SQL Server 2000
  • Microsoft SQL Server 2000 Enterprise Edition (64-bit)
  • Oracle 12g R1 and R2 (12.1 and 12.2) on Windows
  • Oracle 11g R1 and R2 (11.1 and 11.2) on Windows
  • Oracle 10g R1 and R2 (10.1 and 10.2) on Windows
  • Oracle 9i R1 and R2 (9.0.1 and 9.2) on Windows
  • Oracle 8i R2 and R3 (8.1.6 and 8.1.7) on Windows
Domain controller The domain controller must administer both the database server and the client. Network authentication must be provided by NTLM on one of the following operating systems:
  • Windows Server 2016
  • Windows Server 2012
  • Windows Server 2008
  • Windows Server 2003
Client The client must be administered by the same domain controller that administers the database server and must be running on one of the following operating systems:
  • Windows 10
  • Windows Server 2016
  • Windows 8
  • Windows Server 2012
  • Window 7
  • Windows Server 2008
  • Windows Vista
  • Windows Server 2003

To use NTLM authentication, minimal configuration is required after installation of DataDirect Connect for ADO.NET. Refer to the DataDirect Connect Series for ADO.NET User’s Guide for more information.

TitleResults for “How to create a CRG?”Also Available inAlert