SQL Server timestamp column exported to wrong format

[feilbaca]

I'm currently experimenting with exporting from SQL Server to SIARD and back (using dbptk 4.3.0) and have come across an issue with data types.

Many of our tables have a timestamp (aka rowversion) type column, and it's currently being converted into varchar(8). Unfortunately this means that column values are truncated on import resulting in the table inserts failing:

java.sql.BatchUpdateException: String or binary data would be truncated in table 'IIHWTImportTest.dbo.tbAllodyniaSymptoms', column 'AllodyniaSymptoms_Timestamp'. Truncated value: '00000000'.

I believe the correct data type would be varbinary(8). I've amended the metadata.xml to test, and the table data imported successfully.

[dosubot]

Hi, @feilbaca. I'm Dosu, and I'm helping the keeps/dbptk-developer team manage their backlog and am marking this issue as stale.

Issue Summary:

• You reported that exporting SQL Server tables with timestamp (rowversion) columns to SIARD using dbptk 4.3.0 converts these columns to varchar(8).
• This conversion causes truncation errors during import.
• You found that manually changing the data type to varbinary(8) in metadata.xml resolves the issue and allows successful import.
• There has been no further activity or responses on this issue.

Next Steps:

• Please let us know if this issue is still relevant with the latest version of dbptk-developer by commenting here.
• If we do not hear back within 7 days, this issue will be automatically closed.

Thank you for your understanding and contribution!

[feilbaca]

Yes, this is still relevant.

[VitorLelis]

Hey @feilbaca
We've built this artifact that contains the jar with the export types corrections
Can you confirm if it solved the issue?