Table of Contents

Search

  1. Preface
  2. Data Replication Overview
  3. Understanding Data Replication
  4. Sources - Preparation and Replication Considerations
  5. Targets - Preparation and Replication Considerations
  6. Starting the Server Manager
  7. Getting Started with the Data Replication Console
  8. Defining and Managing Server Manager Main Servers and Subservers
  9. Creating and Managing User Accounts
  10. Creating and Managing Connections
  11. Creating Replication Configurations
  12. Materializing Targets with InitialSync
  13. Scheduling and Running Replication Tasks
  14. Implementing Advanced Replication Topologies
  15. Monitoring Data Replication
  16. Managing Replication Configurations
  17. Handling Replication Environment Changes and Failures
  18. Troubleshooting
  19. Data Replication Files and Subdirectories
  20. Data Replication Runtime Parameters
  21. Command Line Parameters for Data Replication Components
  22. Updating Configurations in the Replication Configuration CLI
  23. DDL Statements for Manually Creating Recovery Tables
  24. Sample Scripts for Enabling or Disabling SQL Server Change Data Capture
  25. Glossary

Strategies for Handling Long Column Names

Strategies for Handling Long Column Names

If you have source tables with long column names, alternative strategies are available for handling the long column names so that the corresponding column names on the target do not exceed the maximum length that the target database allows.
Use one of the following strategies to shorten column names in generated audit log tables or target tables on the target:
  • For audit log table columns that contain before- and after-images, use suffixes that are shorter than the default suffixes of _OLD and _NEW. For example, you can use _O and _N as the suffixes.
  • For Merge Apply or SQL Apply mode, create a script that generates regular target tables or audit log tables with shorter column names. In this case, the Data Replication Console cannot map columns based on column names. You must map these columns manually.
  • For replications that use Merge Apply mode with Teradata targets, create views that have shorter column names for the target tables and generate audit log tables based on these views. The column names in the views are truncated, but the Data Replication Console ensures that the names are unique. When defining mappings, map the views to the source tables.

0 COMMENTS

We’d like to hear from you!