Hi Everyone, I'm using a SQL Server connector for ...
# replication-troubleshooting
d
Hi Everyone, I'm using a SQL Server connector for the CDC process, the process is working correctly but the numeric data types of the table were not mapped (recognized), making it impossible to bring the numeric records. I would like some help if it is possible to edit and add the missing fields and data types in the SQL Server connector source? Thanks • Is this your first time deploying Airbyte?: No • OS Version / Instance: Ubuntu • Memory / Disk: 16Gb / 100 Gb • Deployment: Kubernetes deployment? • Airbyte Version: 0.40.18? • Source name/version: Microsoft SQL Server (MSSQL)ALPHA 0.4.26 • Destination name/version: • Step: The issue is happening during creating the source connection • Description: I configured the SQL Server source connector for the CDC process, the CDC is working normally but some numerical columns of the tables do not appear mapped by the SQL Server source connector, in this case the “QT_EQUIP” column. There are other numerical columns with the same problem, I would like some help if it is possible to edit and add the column that the connector didn’t map? • Thanks https://discuss.airbyte.io/t/sqlserver-source-connector-does-not-recognize-data-types/3587
n
Hi Davison! Thanks for your patience - I was out last week for the holidays and am catching up with messages now. Thank you for providing the link to the forum thread and apologies that it took so long to get a response due to the holidays and team members taking time off! For the future, please take note of our code of conduct, double posting goes against it: Rule 3: Don’t double-post. Please be considerate of our community members’ time. We know your question is important, but please keep in mind that Airbyte Slack is not a customer service platform but a community of volunteers who will help you as they are able around their own work schedule. You have access to all the history, so it’s easy to check if your question has already been asked. Let's continue in the forum as that was posted first.
d
I'm sorry, I am new to the Slack community.
n
No worries at all!