|Home » Categories » SQCpack » SQCpack 7|
SP: Issues associated with Time-only Identifier column in a data group
Article Number: 553 | Rating: 5/5 from 1 votes | Last Updated: Sun, Aug 16, 2015 at 2:59 PM
Versions of SQCpack 7 prior to 7.0.15228.1 incorrectly stored a Time-only Identifier in a datetime2 SQL Server column. The datetime2 data type stores both date and time information. When the time-only value was stored in the datetime2 column SQL Server arbitrarily chose a date to use (either a date in 1899 for data imported from SQCpack 6.5, or the current date).
This "extra" date portion caused problems when filtering on a
Time-only Identifier column - there was no error message - but the rows passing
through the filter were incorrectly filtered in most cases.
For versions of SQCpack prior to 7.0.15228.1:
To fix an incorrect Time-only identifier column
7.0.15228.1 and higher performs a one-time migration to fix any incorrect
Time-only identifier column types. After that, if someone uses a version of
SQCpack prior to 7.0.15228.1 to create or import a data group this results in a
Time-only identifier of type datetime2 rather than time(7). Since the one-time
database migration has already been performed (and will not be reapplied) it is
necessary to manually correct these Time-only identifiers as follows.
There are no attachments for this article.