# Why doesn't the SQL Server JDBC Connector support ROWVERSION datatype for timestamp mode?

**URL:** <https://forum.confluent.io/t/why-doesnt-the-sql-server-jdbc-connector-support-rowversion-datatype-for-timestamp-mode/3226>\
**Category:** Managed Connectors\
**Created:** [28 October 2021 15:28 UTC](https://forum.confluent.io/t/why-doesnt-the-sql-server-jdbc-connector-support-rowversion-datatype-for-timestamp-mode/3226 "2021-10-28T15:28:29Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![KyleyJex](https://avatars.discourse-cdn.com/v4/letter/k/3e96dc/32.png) [@KyleyJex](https://forum.confluent.io/u/KyleyJex)\
**Post date:** [28 October 2021 15:28 UTC](https://forum.confluent.io/t/why-doesnt-the-sql-server-jdbc-connector-support-rowversion-datatype-for-timestamp-mode/3226/1 "2021-10-28T15:28:29Z")

</div>

I’m wondering whether someone can explain why the only datatype that is supported for the timestamp column is DATETIME2? I was hoping that the SQL Server JDBC Connector would support ROWVERSION as the timestamp column since this can be managed directly from the database rather than having logic update a separate column when changes are made.

Is it because the Connector only keeps a single value for all tables configured within in Connector properties? If so, is it possible to keep a separate offset value for each table?

Cheers,  
Kyley