5
Vote

Support 2005 and 2008 Side-by-Side (Same PC) Installation

description

Problem:
Unable to use Kimball Slowly Changing Dimension Componet for SSIS 2005 (when installing after 2008 version)
 
Just realized that even when getting the componet to install sucessfully using the binary install, the DLL is named the same regardless of it being 2005 or 2008.
As a result only one DLL (version of the component) is supported per machine.
Including steps to reproduce to assist others who might have encountered this problem.
 
Steps to Reproduce:
  1. Did not use the Kimball_SCD_v1.4 2009-03-09_Setup_2005.msi
    This msi did not work for getting the componnts into the right place to add to BIDS 2005
  2. Copied files from .zip to C:\Program Files\Microsoft SQL Server\90\DTS\PipelineComponents\
  3. Opened the Command Line Utiltiy cmd.exe using Run As... Administrator
  4. Changed directory to C:\Program Files\Microsoft SQL Server\90\DTS\PipelineComponents
  5. Ran command gacutil /i "C:\Program Files\Microsoft SQL Server\90\DTS\PipelineComponents\SSISComponentUtilities.dll"
  6. Ran command gacutil /i "C:\Program Files\Microsoft SQL Server\90\DTS\PipelineComponents\KimballMethodSCD.dll"
  7. Added to BIDS toolbox in Data Flow Transformations section
    a. Right clicked on section of tookbox and selected Choose Items...
    b. On Choose Toolbox Items dialog, selected the SSIS Data Flow Items tab
    c. On SSIS Data Flow Items tab, selected the Kimball Method Slowly Changing Dimension component
    1. Attempted to add Kimball Slowly Changing Dimension Component to SSIS 2005 Data Flow
    2. Received error:
      The component could not be added to the Data Flow task.

    Please verify that this component is properly installed.

    ADDITIONAL INFORMATION:
    The data flow object "MouldingAndMillwork.SSIS.KimballMethodSCD, KimballMethodSCD, Version=1.0.0.0, Culture=neutral, PublicKeyToken=8b0551303405e96c" is not installed correctly on this computer.
    (Microsoft.DataTransformationServices.Design)
  8. Browsed to C:\WINDOWS\assembly (the GAC or Global Assembly Cache)
    a. located KimballMethodSCD

comments

toddmcdermid wrote Mar 25, 2009 at 5:56 PM

I will be determining what exactly has to be "unique" in order to allow side-by-side installations. Hopefully, it's just DLL naming, but I have a feeling it's also class naming. (Get ready for x90 and x100 naming in the code, just like SSIS's API! Whee....)

WeeeBob wrote Jul 16, 2009 at 3:33 PM

Any idea if this feature will make it into 1.5 ? I really need it as I'm upgrading some projects from 2005 to 2008. ta

toddmcdermid wrote Jul 20, 2009 at 5:13 PM

It's on the list to make it in. However, the biggest obstacle I'm going to have is the upgrade path. From what I know now, it looks like I'll have to "break" the component for either 2005 or 2008. One set of users is going to have to do a manual upgrade from v1.4 to v1.5, because (I think that) if the DLL name changes, it's going to be unable to match the new v1.5 version to the old v1.4 version, and won't know that it's the same component, and hence won't upgrade or even run... but we'll see...

If you're upgrading from 2005 to 2008, I'd (presently) recommend you don't install those side-by-side. (Great advice, eh?) Personally, I have a VM loaded with 2005 that I do my 2005 compiling on, and I only have 2008 loaded on my machine.

WeeeBob wrote Jul 21, 2009 at 9:18 AM

yeah no probs, I'll request VM from my IT team to install 2008 on until everything i do moves to 2008. I've come across this problem with two other custom components I use as well. Boooo

toddmcdermid wrote Nov 17, 2009 at 4:11 AM

For those of you whom this is important - please install v1.5 and reply with your experiences...