SQL Server Adapter Guide

Transcription

1 SQL Server Adapter Guide Informatica PowerExchange (Version 8.6)

2 Informatica PowerExchange SQL Server Adapter Guide Version 8.6 June 2008 Copyright (c) Informatica Corporation. All rights reserved. This software and documentation contain proprietary information of Informatica Corporation and are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright law. Reverse engineering of the software is prohibited. No part of this document may be reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica Corporation. This Software may be protected by U.S. and/or international Patents and other Patents Pending. Use, duplication, or disclosure of the Software by the U.S. Government is subject to the restrictions set forth in the applicable software license agreement and as provided in DFARS (a) and (a) (1995), DFARS (c)(1)(ii) (OCT 1988), FAR (a) (1995), FAR , or FAR (ALT III), as applicable. The information in this product or documentation is subject to change without notice. If you find any problems in this product or documentation, please report them to us in writing. Informatica, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer, PowerExchange, PowerMart, Metadata Manager, Informatica Data Quality, Informatica Data Explorer, Informatica B2B Data Exchange and Informatica On Demand are trademarks or registered trademarks of Informatica Corporation in the United States and in jurisdictions throughout the world. All other company and product names may be trade names or trademarks of their respective owners. Copyright, Byte Designs Ltd. All rights reserved. This product includes ICU software which is copyright (c) International Business Machines Corporation and others. All rights reserved. Permissions and limitations regarding this software are subject to terms available at The product includes the zlib library copyright (c) Jean-loup Gailly and Mark Adler. DISCLAIMER: Informatica Corporation provides this documentation as is without warranty of any kind, either express or implied, including, but not limited to, the implied warranties of noninfringement, merchantability, or use for a particular purpose. Informatica Corporation does not warrant that this software or documentation is error free. The information provided in this software or documentation may include technical inaccuracies or typographical errors. The information in this software and documentation is subject to change at any time without notice. Part Number: PWX-MSQ

3 Table of Contents Preface vii Informatica Resources vii Informatica Customer Portal vii Informatica Documentation vii Informatica Web Site vii Informatica Knowledge Base viii Informatica Global Customer Support viii Chapter 1: Overview PowerExchange Batch Change Capture with PowerExchange Change and PowerExchange Real-time Phases of Change Propagation PowerExchange Change Capture Components Software Requirements Chapter 2: Bulk Movement of Data Accessing Microsoft SQL Server Testing a Remote PowerExchange Listener Sourcing Microsoft SQL Server Data Chapter 3: Personal Metadata Using Personal Metadata Chapter 4: Configuring SQL Server Change Data Capture Configuring SQL Server for Change Data Capture Restrictions Configuring PowerExchange for Change Data Capture Configuring the DBMOVER Configuration File Configuring Real-time Extraction Mode Configuring Batch Extraction Mode Configuring Continuous Extraction Mode Implementing SQL Server Change Data Capture Managing Capture Registrations Adding a Capture Registration to an Existing Group Deleting a Registration Group Deleting a Registration Entry Viewing a Registration Group Viewing a Capture Registration Extraction Maps Define the Extraction Process Deleting an Extraction Group or Definition Application Group Table of Contents iii

4 Reset to a New Start Point Migrating to Condense File Extraction Modes Chapter 5: PowerExchange Condense PowerExchange Condense Overview Making Capture Registrations Eligible for Condense Processing Configuring the PowerExchange Condense Process PowerExchange Condense Operational Modes PowerExchange Condense Output Files Configuring PowerExchange Condense Parameters Starting and Stopping PowerExchange Condense Starting PowerExchange Condense Stopping PowerExchange Condense Chapter 6: Managing Change Data Capture Definitions Overview Changing the Underlying Data Source Adding Columns to Capture Registrations Removing Columns from Capture Registrations Modifying Columns in Capture Registrations Changing Extraction Maps Associating Capture Registrations with Extraction Maps Adding or Removing Columns from Extraction Maps Version Indicator in Extraction Definitions Changing Properties of Capture Registrations Amending a Capture Registration Setting to Active Set to History Chapter 7: Accessing CDC Data Accessing Captures Changes Creating Restart Points with DTLUAPPL DTLUAPPL - The Purpose Running DTLUAPPL Adding an Application Modifying an Application Printing an Application Real-time Extraction Mode Testing with the Navigator Using Real-time Extraction Mode in PowerCenter SQL Server CDC Condense File Extraction Chapter 8: Stopping Change Capture Options iv Table of Contents

5 Index Table of Contents v

6 vi Table of Contents

7 Preface This manual is designed to give the required information to develop a Microsoft SQL Server data capture environment and must only be used once all the required steps from the PowerExchange Installation Guide are completed successfully. It is assumed that the PowerExchange Listener is active on the target platform and that it has been tested by use of the Ping utility. The steps required in this manual depends on the functions of the product will be used at this installation. There are two strategies available for refreshing data in a target database: Bulk update using PowerCenter Frequent or near real-time update using data capture techniques PowerCenter or other third-party software can be used to move the data to the target. Informatica Resources Informatica Customer Portal As an Informatica customer, you can access the Informatica Customer Portal site at The site contains product information, user group information, newsletters, access to the Informatica customer support case management system (ATLAS), the Informatica Knowledge Base, Informatica Documentation Center, and access to the Informatica user community. Informatica Documentation The Informatica Documentation team takes every effort to create accurate, usable documentation. If you have questions, comments, or ideas about this documentation, contact the Informatica Documentation team through at infa_documentation@informatica.com. We will use your feedback to improve our documentation. Let us know if we can contact you regarding your comments. Informatica Web Site You can access the Informatica corporate web site at The site contains information about Informatica, its background, upcoming events, and sales offices. You will also find product and partner information. The services area of the site includes important information about technical support, training and education, and implementation services. vii

8 Informatica Knowledge Base As an Informatica customer, you can access the Informatica Knowledge Base at Use the Knowledge Base to search for documented solutions to known technical issues about Informatica products. You can also find answers to frequently asked questions, technical white papers, and technical tips. Informatica Global Customer Support There are many ways to access Informatica Global Customer Support. You can contact a Customer Support Center through telephone, , or the WebSupport Service. Use the following addresses to contact Informatica Global Customer Support: support@informatica.com for technical inquiries support_admin@informatica.com for general customer service requests WebSupport requires a user name and password. You can request a user name and password at Use the following telephone numbers to contact Informatica Global Customer Support: North America / South America Europe / Middle East / Africa Asia / Australia Informatica Corporation Headquarters 100 Cardinal Way Redwood City, California United States Toll Free Standard Rate Brazil: Mexico: United States: Informatica Software Ltd. 6 Waltham Park Waltham Road, White Waltham Maidenhead, Berkshire SL6 3TN United Kingdom Toll Free Standard Rate Belgium: France: Germany: Netherlands: United Kingdom: Informatica Business Solutions Pvt. Ltd. Diamond District Tower B, 3rd Floor 150 Airport Road Bangalore India Toll Free Australia: Singapore: Standard Rate India: viii Preface

9 C HAPTER 1 Overview This chapter includes the following topics: PowerExchange Batch, 1 Change Capture with PowerExchange Change and PowerExchange Real-time, 1 Phases of Change Propagation, 2 Software Requirements, 3 PowerExchange Batch PowerExchange Batch allows you to perform bulk moves of data from data source to target. You can move data from and to UNIX or Linux, Windows, z/os, and i5/os. Change Capture with PowerExchange Change and PowerExchange Real-time Continually repeating the load process through PowerExchange Batch may be costly in terms of space, time, and human resources. What is required is the ability to capture additions, amendments, and deletions to the source data structures and the data itself. In addition, there is a need to ensure that if several changes have taken place, only the latest change is applied. A number of rules are required to ensure that the start point for the changes and the changes themselves can be clearly identified. The change management process must impact on operational systems and procedures. The process needs to be integrated within them to ensure continuous identification and capture of changes. The logical extension of the initial PowerExchange Batch process is PowerExchange Change that retrieves updates at a periodicity set by the user, and the near real-time version PowerExchange Real-time. A variety of components work together to propagate changed data from a source to a target. This section provides a diagram and descriptions of the data-flow and control-flow components of PowerExchange Change. PowerExchange Change and PowerExchange Real-time are both briefly covered here for clarity, however, for MS SQL Server capture, PowerExchange Real-time is the only option. PowerExchange Change is enabled by the CAPX access method from condensed files. PowerExchange Real-time is enabled by the CAPXRT access method direct against the PowerExchange Logger. 1

10 PowerExchange Change and PowerExchange Real-time make data available to be applied to target databases but does not apply the data directly. In these instances, the apply process can be carried out with PowerCenter or a partner tool. The following figure shows how the CAPXRT or CAPX access methods make changes available to PowerCenter so that PowerCenter can apply the changes to the target databases: PowerExchange Navigator CAPTURE REGISTRATIONS EXTRACTION MAPS PowerExchange Real-time Adapters Adabas Datacom DB2 for z/os DB2 for i5/os DB2 for LUW IDMS IMS Oracle SQL Server VSAM LISTENER CAPXRT UOW CLEANSER Push or Pull TCP/IP or MQ PowerExchange Real-time PowerCenter PowerExchange Listener PowerExchange Change Adapters PowerExchange CCT Capture Registrations Adabas Datacom DB2 for z/os DB2 for i5/os IDMS IMS VSAM UOW CLEANSER CONDENSER TASK CONDENSED CHANGES LISTENER CAPX PowerExchange Change PowerCenter Phases of Change Propagation Change capture is the process of capturing changes made to the source database and creating an inventory of those changes in an internal log. PowerExchange Change Capture Components PowerExchange Microsoft SQL Server Capture sources data from Microsoft SQL Server publication technology. Figure 1-1 depicts the PowerExchange Change Capture architecture for a Microsoft SQL Server Capture source that can be applied to a target database using either the PowerCenter Apply feature or a partner product: Figure 1-1. PowerExchange Change Capture Architecture for a Local Microsoft SQL Server Target Key CONTROL FLOW COMPONENT DATA FLOW COMPONENT WINDOWS PowerExchange NAVIGATOR A User Application 1 PowerExchange REGISTRATION DEFINITIONS B Third Party Change Data Consumer SQL Server Database 2 SQL Server Log 3 SQL Server Replication 4 PowerExchange 5 PowerExchange Apply 2 Chapter 1: Overview

11 The components that control the flow of data appear as elliptical shapes with alphabetic labels. These components handle the changed data as it progresses through the propagation process. Some of these components, such as the user application and the source and target databases, are not PowerExchange Change Capture components. Table 1-1 describes the data flow components: Table 1-1. Change Propagation Components Component User Application SQL Database SQL Server Log Replication PowerExchange PowerExchange Navigator PowerExchange Registration Definitions Description Any software that updates the source database on an ongoing basis. The Microsoft SQL Server database where the source data resides. PowerExchange Change Capture can capture changes from more than one source database or data file. Microsoft SQL Server data is captured by utilizing existing Microsoft Publication technology. Microsoft SQL Server uses the logs to source the replication transactions. PowerExchange works with Microsoft publication technology to make changes available for extract. PowerExchange can direct data returned to a number of targets. These may involve passing data to a partner tool to apply the changes to the target, or to use PowerCenter software to apply the data changes directly to the target. PowerExchange Navigator is used to specify the PowerExchange registration, locations, users, and user groups. The central repository holds information on all the data sources and locations. The repository can be created on whatever platform is deemed preferable. To create a data capture environment, complete the following steps: 1. Configure DBMOVER.cfg parameters. 2. Configure Microsoft Replication. 3. Register a data source. 4. Complete Microsoft SQL Server prerequisites. 5. Materialize tables using the Bulk Move facility. 6. Register a restart token. 7. Access the data. For more information, see the PowerExchange Reference Manual. Software Requirements Software requirements for PowerExchange Change Capture and Microsoft SQL Server Capture are Microsoft SQL Server 2000 or greater in the following versions: Enterprise Edition Standard Edition Development Edition Change capture is not compatible with Personal Edition. Software Requirements 3

12 4 Chapter 1: Overview

13 C HAPTER 2 Bulk Movement of Data This chapter includes the following topics: Accessing Microsoft SQL Server, 5 Testing a Remote PowerExchange Listener, 5 Sourcing Microsoft SQL Server Data, 5 Accessing Microsoft SQL Server Before you access Microsoft SQL Server, complete the PowerExchange pre-installation checklist. The name of the distribution server either already in existence or created for PowerExchange capture. The name of the distribution database either already in existence or created for PowerExchange capture. The tables to be sourced and whether they are grouped under a particular owner. The user name and password to access these tables. Testing a Remote PowerExchange Listener To use a remote PowerExchange Listener, it must first be started. To determine if it is started and to check your connectivity, enter the following command at a command prompt: dtlrexe loc=<node> prog=ping In this command, <node> is the Node name in the dbmover.cfg file that points to the remote platform. Sourcing Microsoft SQL Server Data This document covers the following topics, allowing you to capture data, then access that data with PowerExchange tools. The captured data is also available for use by other products, such as ETL tools. To source Microsoft SQL Server data: Obtain the valid user ID and password for the source database. 5

14 Obtain any database specific information, such as Microsoft SQL Server database and server names. Ping the IP address of the source machine to check it is visible. Add a node name for the location in the dbmover.cfg file. Use the command dtlrexe loc=<node> prog=ping uid=<userid> pwd=<pwd> to test that the remote PowerExchange Listener is started, where <node> is the Node name from the dbmover.cfg file. Create the Microsoft SQL Server replication environment if not already used. Use PowerExchange Navigator to create a Personal Metadata Profile for the Microsoft SQL Server source database and view some real data, having checked that the metadata is returned successfully. For more information, see the PowerExchange Navigator User Guide. Use PowerCenter or similar software product to execute the request to move data. 6 Chapter 2: Bulk Movement of Data

15 C HAPTER 3 Personal Metadata This chapter includes the following topic: Using Personal Metadata, 7 Using Personal Metadata You can view Microsoft SQL Server tables and data from the PowerExchange Navigator. To view Personal Metadata, make sure the PowerExchange Navigator can see the data server by adding a new entry to the dbmover.cfg file. By default, the first lines of the file appears as follows: LISTENER=(node1,TCPIP,2480) NODE=(local,TCPIP, ,2480) NODE=(node1,TCPIP, ,2480) NODE=(default,TCPIP,x,2480) If Microsoft SQL Server resides on a machine remote from the PowerExchange Navigator, add a line that specifies the IP address and the PowerExchange Listener started on that machine. To create Personal Metadata to view Microsoft SQL Server data: 1. In the PowerExchange Navigator Resource Explorer, right-click Personal Metadata and click Add Personal Metadata, or click the Add Personal Metadata icon. The Personal Metadata - Name dialog box appears. 2. Enter the following information: Field Name Location Type UserID Password Description Name for the Personal Metadata. Location of Microsoft SQL Server data. This location must also be specified in the dbmover.cfg configuration file. Type of data. Select MSSQL. UserID may not be required. The security requirements are dependant upon the settings of the SECURITY dbmover parameter. For more information about the SECURITY parameter, see the PowerExchange Reference Manual. Password may not be required. The security requirements are dependant upon the settings of the SECURITY dbmover parameter. If the password is left blank but is required then a pop-up password box will appear enabling the password to be given. Leaving the password blank prevents the password being stored by PowerExchange and potentially causing password violations if the Personal Metadata is read after the password for the user has changed. The SECURITY parameter is documented in the PowerExchange Reference Manual. 7

16 Field DSN Database Description Description Data Source Name. The name of the Microsoft SQL Server. Name of the Microsoft SQL Server database. This field is required. An optional description of the metadata. 3. Click Next. 4. To reduce the number of tables returned, enter the Owner or Table name. Qualify the selection if required, and click Finish. If you leave Owner and Table blank, the Navigator returns all tables in the database. The number of tables returned for selection can be narrowed down. If both the Owner and Table are left blank then all tables within the database are returned. Qualify the selection if required and click Finish. The Navigator displays all tables meeting the filter requirements. 5. Click the table you want to use. The columns and column attributes appear. 6. Click the Row Test icon. 7. Review the database information. By default, the row test returns 10 rows. Optionally, change the number of rows returned by the row test, and then click Go. The Navigator returns the specified number of rows from the table. 8 Chapter 3: Personal Metadata

17 C HAPTER 4 Configuring SQL Server Change Data Capture This chapter includes the following topics: Configuring SQL Server for Change Data Capture, 9 Configuring PowerExchange for Change Data Capture, 10 Implementing SQL Server Change Data Capture, 16 Managing Capture Registrations, 17 Extraction Maps, 20 Application Group, 24 Migrating to Condense File Extraction Modes, 26 Configuring SQL Server for Change Data Capture Microsoft SQL Server Prerequisites If the PowerExchange Navigator does not reside on the same box as the Microsoft SQL Server software, then Microsoft SQL Server client software must be installed on the Navigator machine. Microsoft SQL Server must be Microsoft SQL Server 2000 or greater. Microsoft SQL Server Replication must be enabled using the Microsoft SQL Server Publication technology. Required Authority In the absence of a user name and password both the PowerExchange Navigator and capture extract uses Windows authorization to connect to Microsoft SQL Server. Registering items for capture requires system administrator or db_owner authority. For data extract tasks the user must have read access to the distribution database. You require read access to the distribution database for data extraction tasks. Microsoft SQL Server Publications PowerExchange requires that Microsoft SQL Server distribution is enabled on the server from which data is to be captured. To enable distribution through the Microsoft SQL Server Management console, click Tools > Replication > Configure Publishing, Subscribers, and Distribution: 9

18 Alternatively, use the following Microsoft SQL Server supplied stored procedures: sp_adddistributor sp_adddistributiondb sp_adddistpublisher For more information about Microsoft SQL Server Replication technology, see the Microsoft MSDN library on the Microsoft web site. To capture a large number of transaction updates, use a distributed server as the host of the distribution database. Using a dedicated distribution server can avoid competition for CPU and disk storage with a production instance. The default retention period for transactions at the distributor is 72 hours. Informatica recommends that this is increased to 14 days, although the need for resilience will need to be balanced against practical space issues when there is a very high frequency of change. Restrictions The following restrictions apply to SQL Server capture: Capture tables must have a Primary Key. System tables can not be captured. Long columns are not captured in before images. User ID is not captured. Timestamp is that of capture, and not of the original transaction. Tables that include column types of sql_variant cannot be registered for capture. Configuring PowerExchange for Change Data Capture PowerExchange uses the Microsoft SQL Server distribution database to extract captured changes and provides the following extraction options: Real-time extraction mode. When you use real-time extraction mode, PowerExchange reads the changes from the distribution database and continues reading change data until you stop the extraction. Real-time extraction provides the lowest latency for change data extraction. Batch extraction mode from condense files. When you use batch extraction mode from condense files, PowerExchange reads the changes from condense files created by PowerExchange Condense. PowerExchange reads only the closed condense files that existed when the extraction starts and ends the extraction when these condense files have been processed. Batch extraction mode from condense files provides the highest latency for change data extraction. Continuous extraction mode from condense files. When you use continuous extraction mode from condense files, PowerExchange reads the changes from condense files created by PowerExchange Condense. PowerExchange reads data from condense files as it is being written by the condense task, even if the condense file is not yet closed. PowerExchange continues reading changes from condense files until you stop the extraction. Using continuous extraction mode from condense files provides near real-time access to change data. For more information, see PowerExchange Condense on page 29. You can configure PowerExchange for all three extraction modes providing flexibility when choosing an extraction mode for a specific application or set of tables. 10 Chapter 4: Configuring SQL Server Change Data Capture

19 Configuring the DBMOVER Configuration File PowerExchange uses the specifications provided in the DBMOVER configuration file, dbmover.cfg, to configure the operation of various PowerExchange tasks as well as their communication with other PowerExchange tasks. For a complete list of all DBMOVER configuration file parameters, see the PowerExchange Reference Manual. PowerExchange CDC and the PowerExchange Listener use parameters specified in the dbmover.cfg configuration file to: Connect to Microsoft SQL Server databases and tables. Determine the directories in which to store capture registrations, extraction maps, capture files, and condense files. Get connection information in order to extract changes from SQL Server distribution databases and from condense files. PowerExchange Condense has an additional configuration file, dtlca.cfg. For more information, see Configuring PowerExchange Condense Parameters on page 32. To use change data capture, configure the following DBMOVER configuration parameters: Parameter Required Description CAPT_PATH No PowerExchange stores registrations, capture files such as the CCT and CDCT, condense files, and Condense task checkpoint files in the specified directory. Default is the PowerExchange install directory. See CAPT_PATH and CAPT_XTRA Statements on page 11. CAPT_XRTA No PowerExchange stores capture extraction maps in the specified directory. Default is the PowerExchange install directory. See CAPT_PATH and CAPT_XTRA Statements on page 11. CAPI_SRC_DFLT Yes Specifies the default CAPI_CONNECTION PowerExchange uses when none is supplied. Using CAPI_SRC_DFLT, you can specify default CAPI_CONNECTION statements for different source types in a single configuration file. See CAPI_SRC_DFLT Statement on page 12. CAPI_CONNECTION Yes PowerExchange requires CAPI_CONNECTION statements for realtime extraction mode, continuous extraction mode from condense files, and the Condense task. See Required CAPI_CONNECTION Statements on page 12 and CAPI_CONNECTION Statement for Continuous Extraction Mode on page 13. CAPT_PATH and CAPT_XTRA Statements By default, PowerExchange creates all capture files, registrations, and extraction maps in the PowerExchange install directory. Use the following parameters in the PowerExchange DBMOVER configuration file to specify different directories: Parameter CAPT_PATH CAPT_XTRA Description PowerExchange stores registrations, capture files such as the CCT and CDCT, condense files, and Condense task checkpoint files in the specified directory. Create this directory, if it does not exist, prior to using CDC. Default is the PowerExchange install directory. PowerExchange stores capture extraction maps in the specified directory. Create this directory, if it does not exist, prior to using CDC. Default is the PowerExchange install directory. Configuring PowerExchange for Change Data Capture 11

20 Specify these parameters with unique directories to separate CDC objects and files from the PowerExchange code. Separating these data objects and files from the PowerExchange code can ease the software migration process since data objects and files are not inter-mingled with the PowerExchange code. CAPI_SRC_DFLT Statement You can code multiple CAPI connection statements in a single DBMOVER configuration file. Use the CAPI_SRC_DFLT to specify the default CAPI_CONNECTION statement for a specific source type. PowerExchange uses the CAPI_SRC_DFLT statement for a specific source type when no CAPI_CONNECTION override is supplied. The following example shows CAPI_SRC_DFLT statements for multiple source types in a single DBMOVER configuration file: CAPI_SRC_DFLT=(MSQL,sql_name) CAPI_SRC_DFLT=(UDB,db2_name) CAPI_SRC_DFLT=(ORA,uowc_name) To use continuous extraction mode for condense files, the extraction must use a CAPX CAPI_CONNECTION statement. If the CAPI_SRC_DFLT statement points to a source CAPI_CONNECTION, specify the CAPI connection override for the extraction. PowerExchange Condense uses source CAPI_CONNECTION statements. If the CAPI_SRC_DFLT statement points to a CAPX CAPI_CONNECTION, specify the appropriate source CAPI_CONNECTION name in the CONN_OVR parameter in the PowerExchange Condense configuration file. Required CAPI_CONNECTION Statements PowerExchange uses CAPI connection statements to configure CDC processing. SQL Server CDC requires the following CAPI_CONNECTION statements: MSQL CAPI_CONNECTION for real-time extraction mode and for PowerExchange Condense Add the MSQL CAPI_CONNECTION statement to the PowerExchange DBMOVER configuration file, dbmover.cfg, on the machine running SQL Server CDC. For example: CAPI_CONNECTION=(NAME=sql_name,TYPE=(MSQL,DISTDB=distdb,DISTSRV=distsrv)) Note: PowerExchange does not require CAPI_CONNECTION statements on the PowerExchange Navigator machine. You can register tables for CDC and perform database row test functions in Navigator using the remote PowerExchange Listener running on the machine capturing the changes. MSQL CAPI_CONNECTION Parameters Use the MSQL CAPI_CONNECTION statement to specify parameters for Microsoft SQL Server CDC. The MSQL statement has the following syntax: CAPI_CONNECTION=( NAME=name, [DLLTRACE=trace_id], [TRACE=trace], TYPE=(MSQL, DISTDB=distribution_db, DISTSRV=distrib_srv, [DWFLAGS=(flag1,flag2,flag3)], [EOF=Y N], [MEMCACHE=cache_value], [POLWAIT=ssss], [RSTRADV=sssss] ) ) Parameter Required Default Description DISTDB Yes none The name of the distribution database. DISTSRV Yes none The network name of the distribution server. 12 Chapter 4: Configuring SQL Server Change Data Capture

21 Parameter Required Default Description DLLTRACE No none Specifies the name of the TRACE= statement that activates internal DLL tracing for this specific CAPI. Only specify this parameter when instructed to do so by Informatica Global Customer Support. DWFLAGS No none A series of three positional flags with values of Y or N: Flag1 - Warn on data truncation. Y Forces processing to continue if data of an unexpected length is received. The default is N and to stop processing. Flag2 - Warn on schema change. Y Forces processing to continue if schema changes are detected. The default is N and to stop processing. Flag3 - Warn on change data lost. Y Forces processing to continue if the requested start sequence is not found in the transaction log. The default is N and to stop processing. Only use this parameter when instructed to do so by Informatica Global Customer Support. EOF No N Specifies whether PowerExchange ends extractions when end-of-log is reached (EOF=Y) or not (EOF=N). Since this parameter affects all users of the CAPI_CONNECTION, use one of the following methods instead: Specify Idle Time=0 on the PWXPC Real Time application connection. - Specify WAITTIME=0 in the ODBC data source. - Valid values are Y or N. MEMCACHE No 248K Number of Kilobytes to allocate for caching a single row update. Valid values are 1 to NAME Yes none Specifies a unique name for the CAPI_CONNECTION statement. Maximum is 8 characters. POLWAIT No 10 Number of seconds to wait between polling for new data after end of current data has been achieved. Valid values are 1 to RSTRADV No none Specifies the number of seconds PowerExchanger waits before advancing the restart tokens by returning an empty Unit of Work (UOW). Empty UOWs contain no data, only restart tokens. The RSTRADV wait period for a source starts after a UOW for that source is processed and is reset when the next UOW is received or when an empty UOW is returned because the wait period expires, whichever comes first. If RSTRADV is not specified, then PowerExchange does not return empty units of work to help advance the restart point. For example, if you set RSTRADV=5 and a source in the extraction has not had any changes for ten seconds, an empty UOW will be returned for that source after five seconds. This advances the restart point of that source. Warning: Specifying RSTRADV=0 adversely affects performance. With RSTRADV=0, PowerExchange returns empty UOWs after every UOW processed. Valid values are any number of seconds between 0 and TRACE No none Specifies the name of the TRACE= statement that activates the common CAPI tracing. Only specify this parameter when instructed to do so by Informatica Global Customer Support. TYPE Yes none Specify MSQL. CAPI_CONNECTION Statement for Continuous Extraction Mode For continuous extraction mode from condense files, configure CAPX CAPI_CONNECTION statements. For example: Configuring PowerExchange for Change Data Capture 13

22 CAPI_CONNECTION=(NAME=capx_name,TYPE=(CAPX,DFLTINST=collection_id)) Collection_id must match the instance or database name in the PowerExchange Navigator registration group containing the capture registrations. When using continuous extraction mode for condense files, configure the CAPI_SRC_DFLT statement to point to the MSQL CAPI_CONNECTION statement. PowerExchange Condense does not allow CAPI_CONNECTION overrides so the MSQL CAPI connection statement must be the default CAPI connection statement. Note: PowerExchange does not require CAPI_CONNECTION statements on the PowerExchange Navigator machine. You can register tables for CDC and perform database row test functions in Navigator using the remote PowerExchange Listener running on the machine capturing the changes. CAPX CAPI_CONNECTION Parameters The CAPX CAPI_CONNECTION statement specifies the parameters used for continuous extraction from condense files. Using continuous extraction mode from condense files, extractions run near real-time using condense files as the change stream. You can use continuous extraction mode from condense files with DB2 for Linux, UNIX, and Windows CDC, Oracle CDC, and SQL Server CDC. The CAPX statement has the following syntax: CAPI_CONNECTION=( NAME=name, [DLLTRACE=trace_id], [TRACE=trace], TYPE=(CAPX, DFLTINST=collection_id, [FILEWAIT=nnnnn], [RSTRADV=sssss] ) ) Parameter Required Default Description DFLTINST Yes none Specifies the PowerExchange instance to process. For DB2 for Linux, UNIX, and Windows, specify the database from the registration group. For Oracle, specify the collection identifier from the ORACLEID statement or the instance from the registration group. For Microsoft SQL Server, specify the instance from the registration group. DLLTRACE No none Specifies the name of the TRACE= statement that activates internal DLL tracing for this specific CAPI. Only specify this parameter when instructed to do so by Informatica Global Customer Support. FILEWAIT No 1 Specifies the number of seconds to wait before checking for new condense files. Minimum is 1. Maximum is NAME Yes none Specifies a unique name for the CAPI_CONNECTION statement. Minimum is 1 character. Maximum is 8 characters. 14 Chapter 4: Configuring SQL Server Change Data Capture

23 Parameter Required Default Description RSTRADV No none Specifies the number of seconds to wait after receiving a Unit of Work (UOW) for a source in the extraction before advancing the restart tokens by returning an empty UOW. Use this parameter to reduce the amount of data which is reprocessed when restarting the extraction. Default is to advance the restart tokens for a source in the extraction when a UOW for that source is read. Minimum is 0. Maximum is RSTRADV=0 returns empty UOWs regardless of whether the overall restart point has changed. It advances the restart point for every UOW encountered, regardless of whether the overall restart point for the extraction is advanced. Warning: Specifying RSTRADV=0 adversely affects performance. TRACE No none Specifies the name of the TRACE= statement that activates the common CAPI tracing. Only specify this parameter when instructed to do so by Informatica Global Customer Support. TYPE Yes none Specify CAPX. Configuring Real-time Extraction Mode Complete the following steps to configure PowerExchange real-time extraction mode: 1. Configure SQL Server. See Configuring SQL Server for Change Data Capture on page Configure PowerExchange for CDC. For more information about the statements that you need to define, see the following topics: CAPT_PATH and CAPT_XTRA Statements on page 11 CAPI_SRC_DFLT Statement on page 12 Required CAPI_CONNECTION Statements on page Register tables for SQL Server CDC. For more information, see Managing Capture Registrations on page Test the configuration. 5. Configure the PowerCenter extraction by creating mappings and workflows. For more information, see PowerExchange Interfaces for PowerCenter. 6. Establish a starting point in the change stream for the extraction. See Creating Restart Points with DTLUAPPL on page 81. Configuring Batch Extraction Mode Complete the following steps to configure PowerExchange batch extraction mode for condense files: 1. Configure SQL Server. See Configuring SQL Server for Change Data Capture on page Configure PowerExchange for CDC. For more information about the statements that you need to define, see the following topics: CAPT_PATH and CAPT_XTRA Statements on page 11 CAPI_SRC_DFLT Statement on page 12 Required CAPI_CONNECTION Statements on page 12 Configuring the PowerExchange Condense Process on page Register tables for SQL Server CDC selecting Part in the Condense option. Delete and recreate any existing capture registrations. For more information, see Managing Capture Registrations on page 17. Configuring PowerExchange for Change Data Capture 15

24 4. Start PowerExchange Condense. For more information, see Starting and Stopping PowerExchange Condense on page Test the configuration. 6. If migrating from real-time extraction mode, see Migrating to Condense File Extraction Modes on page Configure the PowerCenter extraction by creating mappings and workflows. For more information, see PowerExchange Interfaces for PowerCenter. 8. Establish a starting point in the change stream for the extraction. For more information, see Creating Restart Points with DTLUAPPL on page 81 Configuring Continuous Extraction Mode Complete the following steps to configure PowerExchange continuous extraction mode: 1. Configure SQL Server. For more information, see Configuring SQL Server for Change Data Capture on page Configure PowerExchange for CDC. For more information about the statements that you need to define, see the following topics: CAPT_PATH and CAPT_XTRA Statements on page 11 CAPI_SRC_DFLT Statement on page 12 Required CAPI_CONNECTION Statements on page 12 CAPI_CONNECTION Statement for Continuous Extraction Mode on page 13 Configuring the PowerExchange Condense Process on page Register tables for SQL Server CDC selecting Part in the Condense option. Delete and recreate any existing capture registrations. For more information, see Managing Capture Registrations on page Start PowerExchange Condense. For more information, see Starting and Stopping PowerExchange Condense on page Test the configuration. 6. If migrating from real-time extraction mode, see Migrating to Condense File Extraction Modes on page Configure the PowerCenter extraction by creating mappings and workflows. For more information, see PowerExchange Interfaces for PowerCenter. 8. Establish a starting point in the change stream for the extraction. For more information, see Creating Restart Points with DTLUAPPL on page 81 Implementing SQL Server Change Data Capture Use the following procedure to implement SQL Server change data capture: 1. Amend the dbmover.cfg file on the registration machine. For more information, see Configuring PowerExchange for Change Data Capture on page Configure Microsoft SQL Server Replication. For more information, see Configuring SQL Server for Change Data Capture on page Make sure the Microsoft SQL Server Agent service is running. 4. Register the source using the PowerExchange Navigator. For more information, see Managing Capture Registrations on page Chapter 4: Configuring SQL Server Change Data Capture

25 5. Establish a capture start point. For more information, see Creating Restart Points with DTLUAPPL on page Set the PowerExchange capture registration to Active. Managing Capture Registrations To enable PowerExchange to select the correct changes, you must specify the tables for which the capture collects changes. The registration process consists of a number of tasks, some using the PowerExchange Navigator and others using standard Microsoft SQL Server utilities or Stored Procedures. Creating a Registration Group The registration of the source table is performed using the PowerExchange Navigator. The capture registrations are defined under the Registration Group under Resources on the Resource Explorer panel. A Registration Group is a user-defined group of individual capture registrations. To add a registration group: 1. Use the toolbar Add Registration Group icon or right-click Registration Group and choose Add Registration Group. The Add Registration Group dialog box appears. 2. Enter the following information: Field Name Location Type UserID/Password Registration Server Database Server Registration Server Database Name Description The name of the Registration Group. A Registration Group can have multiple capture registrations. The location of the Microsoft SQL Server Distribution server. Pick a location already defined within the Navigator. Select MSSQL. The user name and password to be used when accessing the Location and the Instance. The Microsoft SQL Server user name must have access to the Microsoft SQL Server location through the Navigator. If the password is left blank the Navigator prompts for the password to be entered as required. The name of the server in which the database from which changes will be captured resides. Select from the list. The name of the database for which changes are captured. Select from the list. 3. Click Next. 4. Enter the following information in the Add Capture Registration - Name and Table Filter dialog box. Use the Table Filter fields to reduce the number of tables returned. If you do not use a table filter, all tables available within the selected database are returned. Qualify the selection if required. Field Description Name Name of this registration within the Registration Group. This is limited to 8 alphanumeric characters. Table Filter Owner The filter criteria will minimize the actual selection list retrieved from the specified Location and Instance. Filter on the table owner, table name or no filter. Filter where possible where the database is known to include many tables otherwise a large amount of information will be returned. Managing Capture Registrations 17

26 Field Table Escape Character Description The required table if known. The escape character that can be used in table names. 5. Click Next. A list of source tables matching the filter conditions appears. 6. Double-click the table you want to register for data capture. There can only be one capture registration for a given source. The columns in the selected table appear. Columns with a key icon are the index columns for that table. To be eligible for data capture, tables must have a primary key. 7. Check Select Column for each column you want to include for capture. When selecting columns for capture, be sure to include all columns you might want to use. An extraction process can select a subset of the captured columns, but it cannot select data that has not been captured. Note: Changes to the table structure after registering the columns require updating the capture registration through versioning. For more information, see Version Indicator in Extraction Definitions on page 42. The following table describes the Tables fields that appear in this dialog box: Tables Field Creator Name Name Type Description Table creator Table name Database object type The following table describes the Columns fields: Columns Field Select Columns NameTC1 Description Indicates whether a column is selected for capture. Column name 8. Click Next. A capture registration can only contain one table. In the Add Capture Registration - Type dialog box, define the type and characteristics of the capture registration. 9. Enter the following information to define the capture registration: Field Condense Status Description Specifies the type of condense processing to do for the capture registration: - None. Indicates that no condense processing is done. - Part. Indicates that condense processing is done and keeps all committed changes for each source row. Status of the capture registration. This can have one of two values: - Inactive. The registration is to be defined but is not to be used by the Collection Agent. This may be done so that a registration is prepared ready for starting capture before the target is materialised (initial data load), and ready to switch to active at the appropriate time. - Active. The registration is effective immediately. 10. Click Finish. In this example, the registration has been added as Inactive. If the registration had been created as active, data would be captured from that point onwards. 18 Chapter 4: Configuring SQL Server Change Data Capture

27 For a more controlled method, create the registration as inactive, perform an initial load of target tables, then change the registration to active at the appropriate time. Each creation of a Registration Group automatically creates a matching extraction group and Application Group with the same name. When defining an actual capture registration for a source the system automatically defines an extraction process for that registration. These default extract definitions can be modified by the user. Once a table is registered and the status of the registration is set to Active, the registration cannot be changed. This is to ensure that the data already collected is not invalidated. To change an existing registration, a new version for the table has to be created and activated. Changes required as a result of changes to the source table are handled by versioning of the registrations. For more information, see Version Indicator in Extraction Definitions on page 42. To change the capture registration status: 1. In the Navigator, select the capture registration. 2. In the Resource Inspector, change the Status as necessary. A small red square appears next to Status. 3. To accept the change, click Apply. The Status changes. The red square clears and an icon next to the registration turns red. 4. When exiting the registration, a prompt appears to save your changes. Click Yes. The Registration saved to the Capture Registration Repository file on the source platform. 5. After the registration is created, you can view it in the Microsoft SQL Server Enterprise Manager. Adding a Capture Registration to an Existing Group To add a capture registration to an existing group: 1. Right click the required Registration Group and click Open. 2. Use the toolbar Add Capture Registration icon. The Add Capture Registration - Name and Table Filter panel appears. 3. Follow Steps 2 to 4 in Managing Capture Registrations on page 17. Deleting a Registration Group Deleting a Registration Group does not delete any Registration Entries. Only group information held locally on the workstation is deleted. You can delete a registration group if there are no active registrations outstanding for the group. To delete a registration group: 1. Select the appropriate Registration Group. 2. Click Delete and click Yes to confirm deletion. 3. Click Yes. Deleting a Registration Entry To delete a registration entry, select the registration entry and click Delete. If the registration is not active you will be asked to confirm the deletion, otherwise you will be prompted to make the registration history before deleting. This will delete the registration entry on the source platform. Data will no longer be picked up by the extraction process. Managing Capture Registrations 19