Toad World® Forums

6.7 version control bug with DATETIME2 precision

Everywhere we have DATETIME2 columns, they are defined with a precision of 0. However, they appear as Modified in Perspectives, with the change being that the precision in the database has allegedly changed to either 6 or 8 while the repository (TFS 2012) shows them (correctly) as 0. SSMS shows them all as still 0 in the database.

This is making things very difficult for us as we can no longer use Toad for checking in any table changes if the table has one or more DATETIME2 columns, as we are seeing many tables in Modified that have not actually changed.

I submitted Service Request # 3528758 for this.