Background:

In our current setup, we have a Sybase ASE environment with a total of 100 tables. Of these, 20 tables are replicated using Sybase Native Replication, which is crucial for our existing data workflows. The replication for these tables is managed via the setreptable command, with the replication state set to true for the 20 tables that require it.

Current Challenge:

When integrating with Fivetran, we aim to include all 100 tables for data synchronization. However, Fivetran's current replication setup logic automatically applies the setreptable tablename, true command to all tables. This results in all 100 tables being marked for replication, regardless of their previous state.

The issue arises when we deactivate replication within Fivetran. The current process indiscriminately sets setreptable tablename, false for all tables, including the 20 tables that were originally configured for Sybase Native Replication. This disrupts our existing replication strategy and causes data synchronization issues.

Impact:

• Disruption of Existing Workflows: The native replication setup for the 20 critical tables is broken, leading to potential data inconsistencies and operational disruptions.
• Manual Intervention: Each time replication is deactivated in Fivetran, manual intervention is required to restore the native replication settings, increasing the risk of errors and administrative overhead.

Proposed Solution:

We request the implementation of a feature within Fivetran that allows for more granular control over table-level replication settings. Specifically:

1. Selective Replication Management: Allow users to specify which tables should have their setreptable state modified by Fivetran, preserving the existing settings for tables managed by Sybase Native Replication.

2. Preservation of Native Replication Settings: Introduce an option to maintain the current replication state of tables that are already configured for native replication, preventing unnecessary disruptions.

3. Customizable Deactivation Process: Provide a mechanism to customize the deactivation process within Fivetran, ensuring that tables critical to existing replication workflows are not affected.

Conclusion:

Implementing these enhancements will significantly improve the flexibility and reliability of Fivetran's integration with Sybase ASE, particularly for environments that rely on a combination of native and external replication strategies. This will ensure seamless data operations and reduce the need for manual corrections