Upgrading Instructions

From v1.5 to v1.6

  1. Download and install the appropriate release for your system.
  2. For each DTSX package that uses the component, perform the following manual steps:
    1. Back up each package
    2. Open the DTSX file in a text editor, such as Notepad.
    3. Search and replace occurrences of the string "KimballMethodSCD" with "DimensionMergeSCD".
    4. Save and close the DTSX file.
Apologies for requiring the manual steps. It was a requirement of following the Kimball Group's request to remove their name from the component.

From v1.4 and earlier to v1.5

  1. Uninstall previous versions of the component.
  2. Follow the v1.5 Installation Instructions to install v1.5 of the component.
  3. For each DTSX package that uses the component, perform the following steps:
    1. Back up the package.
    2. Open the DTSX file in a text editor, such as Notepad.
    3. Search and replace occurrences of the string "SSIS.KimballMethodSCD, KimballMethodSCD, Version=1.0.0.0" to "SSIS.KimballMethodSCD, KimballMethodSCD100, Version=1.0.0.0"
    4. Save and close the DTSX file.
    5. Open your project in BIDS to complete the upgrade.
Apologies for the manual nature of this upgrade process (the editing in Notepad) - it was required to facilitate the future inclusion of feature 2389: Support 2005 and 2008 Side-by-Side (Same PC) Installation.

Last edited Apr 8, 2011 at 5:27 PM by toddmcdermid, version 3

Comments

dave_lumley Apr 18, 2011 at 2:14 PM 
Todd,

Tried to install the 1.6 version on my test server and got the following error when trying to bring the component on the dataflow area.
Could not load type: MouldingAndMillwork.SSIS.DimensionMergeSCDEditorInterface,DimensionMergeSCD100,Version=1.0.0.0,Culture=neutral,PublicKeyToken=8b0551303405e96c. Verify that the component editor is installed properly. (Microsoft Visual Studio)

FYI I did stop and restart both SSIS service and BIDS. How can I fix the issue?

DarrenSQLIS Jun 23, 2010 at 9:31 AM 
Todd, I believe you could also have done this automatically, using the upgrade mappings feature in 2008. Whilst aimed at 2005 to 2008 upgrades it is just a way to change the assembly name. Just an idea.

lkennedy Feb 15, 2010 at 2:04 AM 
I had to add the following steps as the installer put them on the c: drive.
2b. Copy dll's to D:\Program Files\Microsoft SQL Server\100\DTS\PipelineComponents
2c. Run gacutil /i against both dll's. to register them in the correct location.