Since MSAS 2005 makes big changes on dimension modeling, security and etc, how to migrate BI product on MSAS 2005 in short term deems to be a tough task. Let’s make a small web-based BI product which uses VB, ASP and ASPX files as an example.

     Firstly, it is better that you try to use Migration Wizard to migrate your product, if migration can be done automatically, why don’t we use it? Microsoft suggests using Upgrade Advisor which provides more suggestive advice on how to fix the error occurred if you migrated. More detail about Migration and Upgrade Advisor, please reference by the Online Documentation. Please note private dimension and virtual cube will put you in trouble.

     If automatic migration can not work, we have to add more manual tasks. Because DSO should be deprecated, we should discard all codes related to DSO API. There are two solutions we can use. One is rewrite everything in server side, the other is extract DSO functions from the server side to implement by AMO. Obviously, it is not feasible for most projects in short term if we apply for the first solution.

    However DSO is COM wrapped and AMO is .NET based, if we implement all functions previously done by DSO, how can VB and ASP file use them. It is lucky that Microsoft provides interoperate way between COM and .NET assembly, which is CCW (COM Callable Wrapper).

    Of course you will meet with many issues when you plan to implement the wrapper. I give some important issues here, and hope you consider when you start your migration project.

    Writeback table’s column binding

    Private dimension & Role playing dimension

    Cell’s Comment support

    Virtual Cube & Multi-Measure Group

    Hierarchy

    Non-leaf member’s datamember

    [IS_DATAMEMBER] and [DISPLAY_INFO] dimension properties in Parent-Child Dimension

    Upgrade program & Metadata