MS SQL Server: How to keep a Date being a Date


I am new to Airbyte, so this may be a dump question. But unfortunately I am failing to find help in the documentation or via google etc…

The problem is easy to see in the logs:

Posting Date (type datetime[23], nullable false) -> JsonSchemaType({type=string})

Airbyte changes the datatype from datetime to string. This results in the field being a string at the destination (BigQuery) and that results in Looker Studio not being able to treat the field as a Date.

So how do I solve that? I tried multiple different Datatypes on the SQL Server End. I can see the field definition in airbyte, but I am unable to change it.

Thanks for any type of help or pointer to the docs I may have missed.


So I finally found out, that the MS SQL Server Source Connector converts every Dateformat to String. But I also found a part of the docs mentioning, that the basic nomalization converts strings with format label “date-time” to a timestamp.

Thats great news! But how would one ad the format label to the json object during the extract?

Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:

  • It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
  • Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
  • Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
  • We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.

Thank you for your time and attention.
The Community Assistance Team