ODBC drivers to handle more dates and bigint correctly.
Momentarily you have for SQL Server 2 drivers the good one, which is idiotically depreciated and the slower ODBC one, which is "the future" If using the old one bigint, datetime2 datetimeoffset date and time are "TEXT" ODBC converts 2 more datetime2 and date but the rest still is "TEXT" - why ?
thanks Klaus for posting.
Ben is correct and there is a relate item already – please use your votes there.
B. Clothier commented
FYI, voting for this item that is asking for similar functionality and is under review.