Table of Contents

Search

  1. Preface
  2. Introduction to PowerExchange Bulk Data Movement
  3. PowerExchange Listener
  4. Adabas Bulk Data Movement
  5. Datacom Bulk Data Movement
  6. DB2 for i5/OS Bulk Data Movement
  7. DB2 for Linux, UNIX, and Windows Bulk Data Movement
  8. DB2 for z/OS Bulk Data Movement
  9. IDMS Bulk Data Movement
  10. IMS Bulk Data Movement
  11. Microsoft SQL Server Bulk Data Movement
  12. Oracle Bulk Data Movement
  13. Sequential File Bulk Data Movement
  14. VSAM Bulk Data Movement
  15. Writing Data with Fault Tolerance
  16. Monitoring and Tuning Options

Bulk Data Movement Guide

Bulk Data Movement Guide

Introduction to Microsoft SQL Server Bulk Data Movement

Introduction to Microsoft SQL Server Bulk Data Movement

You can optionally use PowerExchange, in conjunction with PowerCenter, to move bulk data from or to a Microsoft SQL Server database on a Windows system. PowerExchange establishes the connection to the SQL Server database for reading or writing data.
You can use PowerCenter without PowerExchange to move SQL Server bulk data. However, using PowerExchange for SQL Server bulk data movement provides the following advantages:
  • PowerExchange provides a connection to SQL Server when a native connection is unavailable on the platform where the PowerCenter Integration Service is running.
  • An ODBC connection is unnecessary.
  • PowerCenter can take advantage of the unique features of PowerExchange connections.
You can use the SQL Server bulk load utility with PowerExchange to efficiently load large amounts of data to SQL Server tables.
Because SQL Server is a relational database, you do not need to create a data map from the PowerExchange Navigator. You can define the bulk data movement entirely from the PowerCenter Designer and Workflow Manager. In the PowerCenter Designer, you can import SQL Server source or target metadata from PowerExchange to create the source or target definitions.
To access a SQL Server source or target, run a PowerExchange Listener on a Windows system and verify that PowerExchange can communicate with it. Also, if you run the PowerExchange Listener on a Windows system that is remote from the SQL Server database, install the Microsoft SQL Server 2012 Native Client on the PowerExchange Listener system. For more information, see Setting Up and Testing Connectivity to a Remote SQL Server Source or Target.

0 COMMENTS

We’d like to hear from you!