Export (0) Print
Expand All
2 out of 2 rated this helpful - Rate this topic

Planning

SQL Server 2012

Enterprise developers who are using on-line transactional processing (OLTP) and business intelligence (BI) technologies can take advantage of the SQL Server data access architecture to connect IBM DB2 databases to new solutions built by using SQL Server integration, analysis, reporting, replication and distributed query technologies. The Data Provider supports SQL commands. This allows for interoperability between COM OLE DB-enabled consumer services and tools in Microsoft SQL Server and remote IBM DB2 relational database management systems. You can execute data definition language (DDL) or data manipulation language (DML) SQL statements that include read and write operations based on dynamic SQL in addition to stored procedures within remote unit of work (RUW) transactions.

Planning various components

Data Provider

Microsoft OLE DB Provider for DB2 Version 4.0 (Data Provider) allows IT professionals and enterprise developers using Microsoft SQL Server Microsoft SQL Server 2012 or Microsoft SQL Server 2008 R2 technologies and tools to access, read, and write vital information stored in IBM DB2 relational database management systems. The Data Provider connects to DB2 using an underlying Microsoft network client for DB2 that functions as a DB2 DRDA Application Requester.

DB2 Servers

You can use the Data Provider to interact with IBM DB2 database servers on the following platforms using a DRDA over TCP/IP network connection.

  • IBM DB2 for z/OS V8.1, V9.1, and V10

  • IBM DB2 for i5/OS V5R4, V6R1, and V7R1

  • IBM DB2 for Windows, AIX, HP-UX, Solaris, Linux V9.1, V9.5, and V9.7

The Data Provider is designed and tested for use with Microsoft SQL Server 2012 and SQL Server 2008 R2. The Data Provider is based on technology in Microsoft Host Integration Server 2010. For more information about HIS 2010, see Host Integration Server 2010 (http://go.microsoft.com/fwlink/?LinkID=180445).

SQL Server Products

The Data Provider requires the following Microsoft SQL Server software products as installation dependencies.

  • Microsoft SQL Server 2012 Enterprise, Developer or Evaluation Edition

  • Microsoft SQL Server 2008 R2 Datacenter, Enterprise, Developer or Evaluation Edition

The Data Provider must be installed on the same computer as SQL Server 2012 or SQL Server 2008 R2 for use in-process with the Data Consumer application.

SQL Server Data Consumers

SQL Server Integration Services, SQL Server Analysis Services, and SQL Server Reporting Services interact indirectly with the Data Provider through the Microsoft ADO.NET Data Provider for OLE DB. Distributed query processing interacts with the Data Provider directly through OLE DB. SQL Server Replication requires a DQP-defined linked server for specifying the initial connectivity information, but will use ADO.NET to OLE DB integration at run time when synchronizing data. SQL Server provides a rich array of tools that you can use to create DB2 solutions with SQL Server consumers.

Data Conversion

The Data Provider converts to and from DRDA formatted data types and OLE DB data types. Depending on the SQL Server Consumer, IT professionals can control the conversion using an XML data type mapping configuration file or SQL Server data type mapping system table.

Code Page Conversion

Organizations often have to develop solutions that are globalized for deployment in multiple locales. IT professionals can configure the Data Provider to process string conversions based on standard Coded Character Set Identifiers (CCSIDs) and code pages, including support for single-byte, mixed-byte, double-byte, EBCDIC, ANSI, OEM PC, UNICODE, Arabic and Hebrew bi-directional layout conversion.

Security

Enterprise IT organizations seek ways to secure the authentication credentials and user data that flows across the network. The Data Provider offers technologies for authentication encryption, data encryption, or both authentication and data encryption. IT professionals can configure the Data Provider to use 256-bit Advanced Encryption Standard (AES) to secure the authentication credentials, as well as 56-bit Data Encryption Standard (DES) to secure both the authentication credentials and user data. At the TCP/IP network layer, the Data Provider supports either Secure Sockets Layer (Version 3.0) or Transport Layer Security (TLS Version 1.0) to encrypt both authentication credentials and user data. The Data Provider supports optional use of Enterprise Single Sign-On Version 4.5 to map foreign credentials (e.g. RACF Username) to Windows Active directory credentials. ESSO is a separately installable feature of Microsoft Host Integration Server 2010 licensed as supplemental technology to Microsoft BizTalk Server 2010. For more information about HIS 2010, see Host Integration Server 2010 (http://go.microsoft.com/fwlink/?LinkID=180445).

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.