Migrate to SQL 2005 terminates on trivial error
Rob Evans
terminated with a message that a date was out of range - no indication
as to which record (let alone field) was the cause, though it was
while processing FILE records (of which there were many thousands).
After some investigation, aided by looking at the records created in
the new database, I discovered a date field in a record in the source
database that was negative - therefore "out of range".
The affected field represents the date-stamp of the file when added to
the project. I replaced the value in the field with the corresponding
value from the previous record, and the migrate proceeded to a
successful completion.
Such a trivial error should not have caused a complete failure of the
migration or there should, at least, have been more details of the
record (& field) in error.
Side-lights of this problem and my correcting the field were, when
looking at the project in the production environment on SQL Server
2000, that:
1) beforehand, the file was not actually visible in the StarTeam
Client (there was only one revision of the file, and it had the bad
date);
2) after correcting the date (in the production database), the file
became visible in the StarTeam Client but the date displayed as some
time in the year 1617 (the -ve value must have been held in cache
somewhere, and could be interpreted reasonably);
3) it took a stop and restart of the configuration on the StarTeam
server for the date field to display properly in the StarTeam Client.
Note, this is just a cautionary tale, entered in case it is of help to
some other poor sole who runs into a similar problem.
--
Regards, Rob E.