DocsData SourcesBest Practices

Best Practices for SyncSage Users

Follow these best practices to optimize your data integration experience with SyncSage.

7.1 Security

  • ๐Ÿ”’
    Rotate Credentials

    Change passwords/API keys every 90 days.

    Tip: Set up a calendar reminder to regularly update your credentials. This helps prevent unauthorized access if credentials are ever compromised.
  • ๐Ÿ”’
    Whitelist IPs

    Allow SyncSage's IP ranges in your firewall.

    SyncSage IP Ranges:
    • 52.x.x.x/24
    • 54.x.x.x/24
    • 35.x.x.x/24

    Contact support for the exact IP ranges for your region.

7.2 Cost Control

  • Incremental Syncs

    Set for large datasets (e.g., sync only new Salesforce leads).

    Example Configuration:
    {
      "sync_mode": "incremental",
      "cursor_field": "last_modified_date",
      "cursor_granularity": "seconds"
    }
  • Auto-Suspend

    Use in Snowflake to save costs during idle periods.

    Snowflake Command:
    ALTER WAREHOUSE FIVETRAN_WH 
    SET AUTO_SUSPEND = 300; -- Suspend after 5 minutes of inactivity

7.3 Optimize Performance

  • Off-Peak Syncs

    Schedule syncs during off-peak hours (e.g., 2 AM).

    Benefits:
    • Reduced impact on source system performance
    • Lower latency for sync operations
    • Minimized conflicts with other processes
  • Query History

    Use the Query History tab in Snowflake to identify slow queries.

    Snowflake Query:
    SELECT query_id, query_text, execution_time, error_code
    FROM table(information_schema.query_history())
    WHERE execution_time > 60000 -- Queries taking more than 60 seconds
    ORDER BY start_time DESC
    LIMIT 20;

Troubleshooting Common Issues

IssueHow to Fix in SyncSage
Sync FailedCheck the Alerts tab for error details.
Missing DataVerify field mappings in the pipeline.
Slow SyncsReduce sync frequency or contact support.