MSSQL Destination Connector

satyampurwar commented 3 years ago

Tell us about the new integration you’d like to have

Which source and which destination?

Please help in building the MSSQL Destination connector as the general documentation around building source connector is not guiding enough to build destination connectors.

Do you need a specific version of the underlying data source e.g: you specifically need support for an older version of the API or DB?

Describe the context around this new integration

Which team in your company wants this integration, what for? This helps us understand the use case.
How often do you want to run syncs?
If this is an API source connector, which entities/endpoints do you need supported?

Describe the alternative you are considering or using

What are you considering doing if you don’t have this integration through Airbyte?

satyampurwar commented 3 years ago

MSSQL - Source (I can see this) >>> Extract MSSQL - Destination (this is missing) >>> Load Purpose - I am doing research, evaluating data engineering pipelines and searching open source ETL tools which can easily fit into any use case when there is a need Sync - Automatic + On-demand

jrhizor commented 3 years ago

duplicate of https://github.com/airbytehq/airbyte/issues/613 ?

sherifnada commented 3 years ago

@satyampurwar Let me look into what it would take to do MSSQL destination and get back to you soon.

cgardens commented 3 years ago

closed by https://github.com/airbytehq/airbyte/pull/3195

airbytehq / airbyte