I am running IA on AIX with ODBC pointed at SQL Server.
Some columns have TIMESTAMP data type, and IA reports such columns as data type "BINARY" with length "8" and status as "Cannot Analyze" and "Not Analyzed." Why is this? Is there a way to get IA to process these columns? When you View Sample Data from IA, they display OK.
SQL Server DATETIME columns on the other hand import and display in IA just fine and column analysis runs well on those types.
The ODBC driver I am using is .../branded_odbc/lib/VMsqls00.so
Description=DataDirect SQL Server Native Wire Protocol
IA and ODBC SQL Server TIMESTAMP data type
IA and ODBC SQL Server TIMESTAMP data type
Choose a job you love, and you will never have to work a day in your life. - Confucius
I am getting an idea from google that Microsoft TIMESTAMP data types are not timestamps at all but rather are just some sort of "rowversion" counter. That might explain why all the binary columns in each table are named "rowversion." Really, Microsoft? Really?
Choose a job you love, and you will never have to work a day in your life. - Confucius