keif888 / ssismhash Goto Github PK

I have done a Custom install of Multiple Hash, but it does not show up in the SSIS Tool box for Data Flows. Please help me resolve this issue. The specifics of my install and the actions I have taken are described below.

I installed SQL Server 2016 on a Windows 2012R2 64 bit server the same way I have for prior versions of SQL Server, where the Shared Feature directories are in C:\Program Files\Microsoft SQL Server and C:\Program Files (x86)\Microsoft SQL Server, but the Instance Root Directory is in D:\Program Files\MySQLinstanceName.

Then I installed the MultipleHashInstallerx64_20170713_V1.7.1.0.msi, also the same way I have for prior versions of Multiple Hash and SQL Server, choosing Custom Install and choosing C:\Program Files\Microsoft SQL Server\130\DTS and C:\Program Files (x86)\Microsoft SQL Server\130\DTS for the Install locations.

After the install, I can see the MultipleHash2016.dll file in the PipelineComponents folder in the install locations.

When I open up SSDT 2015, I do not see Multiple Hash in the SSIS Toolbox Data Flow options.

Where should I have installed the Multiple Hash items?
Will I need to uninstall Multiple Hash and re-install it, or can I just move or copy the .dll files to the appropriate location?

If I installed them in the appropriate locations, what do I need to do so that Multiple Hash appears in the SSIS Toolbox for Data Flows?

I tried also installing MultipleHashInstallerx32_20170713_V1.7.1.0.msi, and I tried rebooting after the installs, but neither of those actions fixed the problem.

I also tried activating the Multiple Hash component within SSDT, but could not find a way to do this.
Right-clicking on "Common" or on "Other Transforms" (there is no "Data Flow Transformations" in SSDT 2015) gives only the option to "Refresh Toolbox". I tried this, but Multiple Hash does not appear in the Toolbox. I tried to activate it in SSDT using the Tools > Choose Toolbox Items menu options, but there is no "SSIS Data Flow Items" tab, and I did not find Multiple Hash on any of the tabs that did display.

After upgrading our local machines to MultipleHash 1.7.3, VS2017 successfully loads the component and it will run locally; however, after deploying the upgraded packages to the SSIS Server, it fails to run reporting, "The component is missing, not registered, not upgradeable, or missing required interfaces." The server is running Microsoft SQL Server 2016 (SP1-CU7-GDR) (KB4057119) - 13.0.4466.4 (X64) Enterprise Edition (64-bit) on Windows Server 2012 R2 Standard 6.3 (Build 9600: ) (Hypervisor).

We are generating the checksum of a combination of two columns (ID an int containing 1002, ContactMethod a varchar containing ‘Email’).

SSIS
The sha512 checksum generated with SSIS Multiple Hash through SSIS is 1F32BFEA7D50117E2036E9CACF06FC24FB8F483B5BDD2C094C395DD88247D546E02678D898FD64227236C24D95746275510653012545D480E6D2A9B00D808C31

ADF/Snowflake
The sha2(512( checksum generated through ADF and Snowflake are identical but different than the one generated through SSIS above.
select sha2('10002Email',512);
4cb3b1d676eb2750b0d0f38b5fbf8c6267578cb4c70e450bbf9e923c5932aa7b59b97f59865f610f2ed53247483f7c0f7237150c4e9d0324791ea9ec9425cb0e

Does anyone know what is going on? Our suspicion is the string used as input in SSIS may be decorated with delimiters and be different than ‘10002Email’. Any insight would be greatly appreciated.

We are migrating from SSIS/SQL Server to ADF/Snowflake.

I have a server I am trying to install this package on.
MS Windows Server 2019 Datacenter
10.0.17763 Build 17763
Microsoft SQL Server 2019 (RTM-CU5) (KB4552255) - 15.0.4043.16 (X64)
Microsoft Visual Studio Enterprise 2019 Version 16.6.5
Microsoft ,Net 4.8.03761

When I load the solution I get an error that MultipleHash2008 is not compatible with .Net 4.6.1
and then when I get to the solution explorer I see that the MultipleHashInsterx32 and MultipleHashInsterx64 show as "incompatible"

How do I install this package?

I'm working on a newer SSIS project using version of VS 2017 SSDT (Version 15.5.2) targeting SQL Server 2017. The machine has Windows 2012 R2 Datacenter. I am using 1.7.2.0 of Multiple Hash. I cannot selectively choose hash columns to include in the hash. I am only able to select all columns in the column header.

Hi, we're using the multiple hash component in our data warehouse SSIS project. Our data warehouse is a data vault and the best practice for hashing using this technique is to remove the trailing NULL values as well as adding a delimiter (like pipe delimiter |) between each columns. How does it work if we want to add these options to the multiple hash component? Can we add it to the git code or do we have to maintain a separate code base? Also, are there any licensing implied into doing this?

Thanks,
Christian Cote

I am trying to install this component to the Azure SSIS runtime.

I'm following the instructions from here:
https://docs.microsoft.com/en-us/azure/data-factory/how-to-configure-azure-ssis-ir-custom-setup

I have a main.cmd file with this in it (on one line):

msiexec /i MultipleHashInstallerx64.msi /qn /lv %CUSTOM_SETUP_SCRIPT_LOG_DIR%\MultipleHashInstall.LOG

I can see the MultipleHashInstall.LOG appearing in blob storage (attached) and is populated with a lot of stuff that looks like it's installing. The Azure SSIS runtime starts OK (it won't start if there is an installation error)

With regards to the packages, I have installed the 32 bit version of MultipleHash on my workstation, opened and upgraded my packages in SSDT 15.5.7 and also set the deployment target to SQL 2017

I've deployed to SSIS Azure but I get these in the SSIS log when running in SSIS Azure:

Load Staging Purchase:Error: The managed pipeline component "MultipleHash" could not be loaded.  The exception was: Could not load type 'MultipleHash' from assembly 'Microsoft.SqlServer.PipelineHost, Version=14.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91'..

Load Staging Billing:Error: The component metadata for "MD5 Hash" could not be upgraded to the newer version of the component. The PerformUpgrade method failed.

Load Staging Billing:Error: The component is missing, not registered, not upgradeable, or missing required interfaces. The contact information for this component is "http://ssismhash.codeplex.com/".

Load Staging Billing:Error: Component MD5 Hash, clsid {8DC69D45-2AD5-40C6-AAEC-25722F92D6FC} failed to initialize due to error 0xC0047067 "The "%1" failed to cache the

Load Staging Billing:Error: Component MD5 Hash, clsid {8DC69D45-2AD5-40C6-AAEC-25722F92D6FC} failed to initialize due to error 0xC0047067 "The "%1" failed to cache the component metadata object and returned error code 0x%2!8.8X!.".

Load Staging Billing:Error: The "MD5 Hash" failed to cache the component metadata object and returned error code 0x80131600.
Load Staging Billing:Error: The managed pipeline component "MultipleHash" could not be loaded.  The exception was: Could not load type 'MultipleHash' from assembly 'Microsoft.SqlServer.PipelineHost, Version=14.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91'..

I see an upgrade message in there - I don't understand why it's trying to upgrade.

In the DTSX,
PackageFormatVersion=8
LastModifiedProductVersion=14.0

I've tried both the 32 and 64 bit installers.

MultipleHashInstall.LOG

I installed the latest version of MultiHash64 on my local machine and can run my SSIS packages successfully. We recently updated the server to SQL Server 2019 and installed MultiHash64 on the server. When I run my package on the server I receive errors.

"Data Flow Task - Load Stage From SAP:Error: Multiple Hash failed validation and returned error code 0xC0048021."

"Data Flow Task - Load Stage From SAP:Error: The component is missing, not registered, not upgradeable, or missing required interfaces. The contact information for this component is "http://ssismhash.codeplex.com/"."

"Data Flow Task - Load Stage From SAP:Error: The component metadata for "Multiple Hash" could not be upgraded to the newer version of the component. The PerformUpgrade method failed."

I modified the location of my SQL Server 2017 installation directory (I made it the same folder, but on the D drive). The Multi-Hash installer installed to the C Drive. When I copied the DLLs to the corresponding folder on the D Drive, the transform appeared in VS 2017 as expected.

Hi,

After installing SSDT17.1 (build 14.0.61705.170) on a machine with VS2015 already installed, the Multiple Hash component is missing from the SSIS Toolbox. Packages that we're created earlier using this transform still execute fine but can't be modified anymore.

The packages are targeted to run at SQL Server 2016.

Is it possible to get an update for the Multiple Hash Transform using SSDT17.1 ?

Hello, are you planning SSISMHash support for SQL 2019?

Hi - I wondered if you have any plans to support the latest version of SSDT (17.2) with your MultipleHash component in Visual Studio 2015?

Regards,
Matt Boler

Hi Keith,

Reading the changelog history since 1.6.6.4 where you started supporting SQL 2016 RTM I don't see any mention for SQL 2016 SP1. Our new SQL 2016 environment is up-to-date (SP1 CU4) and will be following an strict updating policy, so before installing I just wanted to be sure that your latest version solution is supported or on the contrary, if you need to test and especifically support any new SP or CU as those are being released.

Thanks for your time and the great work.

Hi, i would like to be able to specify a number of threads, instead of only having 1, Auto or On (when using your component programatically). It'd be nice to be able to set Auto-threading with a lower threshold than the number of processing cores, considering i might have 4 packages going with 8 hash components simultaneously - on a 32 thread system, i might prefer to say 4 threads max per instance of the component.

Thanks

Hello,
We are updating 232+ SSIS Packages from VS 2008 to VS 2017. Is there a way to migrate the SSISMHash 2008 to 2017 without having to re-create and map from scratch in the dataflow the SSISMHash 2017 ?
I tried to mess around the package XML code to change the SSISMHash properties but it did not work.
Thanks
Laurent

Was curious if there was any plans to support other hashing algorithms like Murmur for example?

I recently updated to the latest multiple hash version - 1.7.5. However, it still shows as version 1.7.2. on the about menu.
I uninstalled the older version and installed this new version but the about menu still shows 1.7.2

I am using visual studio 2015 with projects targetserver version = 2016

Is this a known issue?

would there be any possibility of getting a digital signature added to MultipleHashInstallerx64.msi v1.7.5.0 ? our group policy is not to allow unsigned applications to be installed.

Never mind ... missed the fact that this was resolved in closed issue with the latest release

Hi Keith,

I have installed Multiplehash v1.7.2 as Complete install as previously had v1.7.0 which has been uninstalled.

The issue is the 1.7.2 is not showing up in: C:\Program Files (x86)\Microsoft SQL Server\140\DTS\PipelineComponents and
C:\Program Files (x86)\Microsoft SQL Server\140\DTS\UpgradeMappings are missing the xml extentions.

However it successfully shows up on all other folders e.g. 100,110,120,130.

Is their an issue with the installer? And how do we overcome this issue?

As I expected this to appear in their and avoid any upgrade errors due to target server version defaulting to SQL Server 2017.

Thanks

32 bit installer (typical install) succeeds but afterward the component doesn't appear in SSDT (VS2010). Looked in PipelineComponents folder (C:\Program Files (x86)\Microsoft SQL Server\110\DTS\PipelineComponents) but didn't find the multiple hash dll there so I suspect that the installer is quietly failing (or installing somewhere else?).

Tried the custom install to confirm that the installation path is correct (i.e., as noted above) and it was.

As a feature request I would like to have a check box associated with each output column to have the hash output base64 encoded, and therefor a (n)varchar datatype.

For me this would be useful where the hash is going to be used in an XML document, and more generally can make debugging a little easier when comparing hash results.

The attached screen shot shows the related version information. After attempting multiple installs and uninstalls of 1.7.2 (complete, typical, and custom), I cannot seem to get the extension to show up in SSIS Toolbox, nor is the component editable in an existing SSIS package.

The DLLs are installed in the GAC.
C:\Program Files\Microsoft SQL Server\130\DTS\UpgradeMappings contains: SSISMHash.xml & SSISMHash.extensions.xml
C:\Program Files\Microsoft SQL Server\130\DTS\PipelineComponents contains: MultipleHash2016.dll

Of note is the entry in SSISMHash.xml that seems to indicate that the mapping entry for SQL Server 2016 exists in the same file, but in a different location (%ProgramFiles%\Microsoft SQL Server\120\DTS\UpgradeMappings\

On this machine, there is no 120 folder, since this was a clean install of SQL Server 2016, Visual Studio 2017 and SSMS 2017.

Any ideas?

Would you be able to support sql server 2022 please.