Suggest an Idea

[zwatkinscovermymeds]

A majority of my task in Qlik Replicate consist of a PostgreSQL source replicating to a SQL Server target. the vast majority of my PostgreSQL source tables consist of timestamp with TZ datatype. this datatype stores the timestamp value with a timezone offset. When that is replicated over to my SQL Server target, Qlik Replicate adds (or subtracts) the timezone offset converting the datetime to UTC. Why does Qlik Replicate not support the datetimeoffset datatype in SQL Server? Currently, have ~80 task where I am having this issue. When we made the move to Qlik Replicate this presented a lot of manual work to Sql Server stored procedures to account for the new time affecting or client reporting.

My understanding is that PostgreSQL and SQL Server are mature endpoints for Qlik/Attunity, so I don't understand why I this datatype is not supported. Am I the only one with this issue? Has this been solved already?

[seanhawkes]

yea this seems like a no brainer.  please add

[Shelley_Brennan]

Thank you for the suggestion.  We are collecting feedback and will update when we have it on the roadmap.

[LaurentSamyn]

Same thing required with Oracle and others would be great...

[karrasan]

I strongly agree please add it

[Huey]

Bump

[zwatkinscovermymeds]

This is still an issues. I would love to see this addressed in the next update 🙂 

[Meghann_MacDonald]

From now on, please track this idea from the Ideation portal. 

Link to new idea

Meghann

NOTE: Upon clicking this link 2 tabs may open - please feel free to close the one with a login page. If you only see 1 tab with the login page, please try clicking this link first: Authenticate me! then try the link above again. Ensure pop-up blocker is off.