Open cnlee1702 opened 4 months ago
Might not be related to dbt?: https://stackoverflow.com/questions/12063850/multiple-timestamp-columns-in-sql-server-2000 Cast to datetime2 datatypes in the view might help solve the issues.
@ericmuijsvanoord thank you for looking into this.
Unfortunately casting to datatime2
did not work in this case.
SQL Error [529] [S0002]: Explicit conversion from data type timestamp to datetime2 is not allowed.
Was the first time encountering this issue. Sounds like also not a common issue on your end?
Looks like a data source anomaly that I'll work around some other way. Thanks!
timestamp is some internal database type that tracks changes on a table. Basically it is not "data" but more metadata on the table by the sql server engine. It is handy for tracking changes so you might be able to search and fine a way to convert it to datetime or integer for tracking changes.
Overriding the column datatype to BIGINT
with the union_relations dbt-utils
macro will likely be a viable path with this source data.
Again -- I great appreciate your efforts looking into this @ericmuijsvanoord!
dbt snapshot
not working with SQL Server 2019 using a source table containing atimestamp
column.dbt snapshot
Error message
SQL Server version