0 comments
Various 
Last period we have a small project to migrate a number of SQL2000 cubes to SQL2005 cubes. We have Oracle as datasource. During the migration we have several issues detected. So will MDX statements be migrated to text. When we process the cubes we have an error called "parent columns and child columns don't have type matching columns".
We did some research to find out what the problem is and how to solve it. The problem is dat Oracle datatype decimal is not translated in the SQL Environment as a decimal. Actualy it is a kind of variance. During the migration the datatype Decimal is translated in different kind of SQL Server 2005 datatypes like int32, int64 etc, you can't normally simple change a datatype, cause theire attributes can be referenced by another table. So the problem is that two attributes that are referenced each other have a different datatype. To correct his , you have to break the reference and refresh the table, so the datatype will be assigned and recreate. You have to do this from the outside to the inside. It could be a lot of work to do, but it make it possible to build youre cube.