I have to concur, this is rather frustrating. I have spent almost 9 hours now tracking this one issue down to run scripts before the upgrade which did not resolve the problem to a hot fix to now having to determine what data in a numeric column is not numeric. I don't see how that's even possible unless the data was in a non numeric column and was to be split during the upgrade into two columns but someone did not write the code correctly to do that. The upgrade we are running will involve over 59 company databases and we cannot afford to be tracking something like this down on every upgrade. Someone needs to take notice of this and resolve this immediately. When you say something is resolved, we are relying on that information, if it was fixed in the July hotfix it is broken again in the October one. Please get this right and soon!!
↧