Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

New Destination: AWS Babelfish as destination

Handerson Dutra User

Hi support team. We're currently trying to sync data from Sql server to AWS Babelfish (Sql server). Even though Babelfish uses Aurora Postgres as its backend, it created custom data types unsupported by Fivetran, and the sync process from Sql Server to Postgresql is impossible.

The second option would be using Babelfish endpoint, which mimics a sql server database. However, at the destination validation process, Fivetran does not recognize it as a Sql Server database and the process fails (see ticket id  #160486).

That being said, I would suggest that Fivetran should add a new destination to Babelfish.

Please sign in to leave a comment.

Comments

1 comment

Date Votes
  • Eric O'Connor Fivetranner
    • Edited

    Hi Handerson,

    > Even though Babelfish uses Aurora Postgres as its backend, it created custom data types unsupported by Fivetran, and the sync process from Sql Server to Postgresql is impossible.

    Can you clarify the architecture here? As I understand it, a connector from SQL Server to Aurora Postgres should not involve Babelfish at all:

    Fivetran does support SQL Server as a source, and also supports Postgres as a destination. Is there a reason you cannot sync data from SQL Server → Postgres without involving the AWS Babelfish layer?