Version 1.1.000 with SQL2016 support

Rating:        Based on 4 ratings
Reviewed:  4 reviews
Downloads: 2781
Change Set: d6576f315b5f
Released: Jul 24, 2016
Updated: Feb 3, 2017 by webking
Dev status: Stable Help Icon

Recommended Download

Application DLL Pack
application, 4658K, uploaded Feb 3 - 2781 downloads

Release Notes

Automatic installer

Due to some problems of false positives, automatic MSI installer has been removed. Unfortunately, some antivirus scanners are not smart enough to classify binaries, therefore I decided to drop the installer and to rely only on DLL manual installation. Please look at the following instructions for installing the component.

If you have any question, please contact me via email, using the appropriate form.

Manual Installation

This process isn't that complex, but requires some attention. The entire installation process is composed by the following steps:
  1. Check Requirements
  2. Download the DLL Pack
  3. Copy DLL into MS SQL DTS path
  4. Register DLLs into the GAC

We will go through each one in order to make the installation process as smooth as possible.

Preliminary step: requirements and download.

At the time of writing, JSONSource supports MS SQL Server 2012, MS SQL Server 2014, and MS SQL 2016 with .NET 4.0 framework. If you are using a different MS SQL version, or a different .NET framework, this component will not show up into the Visual Studio SSIS ToolBox.
Beside, for the further steps of the installation, it is crucial to understand which version of MSSQL Server are you going to use. If you are not sure about which version of MS SQL Server is installed on your system, please follow this guide

Once you know your MS SQL Server version, you can download the DLL Pack. As you will see, it contains different folders. Each subforlder contains the required DLL to be installed in order to enable the JSONSource component on different MS SQL Server versions. This means that you need to pick one sub folder and install the contained DLL, as explained later.
The mapping between the MSSQL Version and the MS SQL Name is shown in the following table.

MS Sql Name MS Sql Version DLL Pack folder Default DTS Installation Path
SQL Server 2016 (x32) 13.X 130 C:\Program Files (x86)\Microsoft SQL Server\130\DTS\PipelineComponents
SQL Server 2016 (x64) 13.X 130 C:\Program Files\Microsoft SQL Server\130\DTS\PipelineComponents
SQL Server 2014 (x32) 12.X 120 C:\Program Files (x86)\Microsoft SQL Server\120\DTS\PipelineComponents
SQL Server 2014 (x64) 12.X 120 C:\Program Files\Microsoft SQL Server\120\DTS\PipelineComponents
SQL Server 2012 (x32) 11.X 110 C:\Program Files (x86)\Microsoft SQL Server\110\DTS\PipelineComponents
SQL Server 2012 (x64) 11.X 110 C:\Program Files\Microsoft SQL Server\110\DTS\PipelineComponents

Copying the DLL.

In order to make JSONSOurce to work you need to copy all the DLL of the selected MS SQL Version into its appropriate installation folder. The table above shows the default directory where you should dopy the DLLs for each supported MS SQL Version. For the sake of clarity, we'll make an example. Let the DLL pack reside on the desktop. Let's assume we have MS SQL Server 2014 both in x32 and x64 versions. By looking at the table we realize we need the DLLs contained into the folder "120". So, we copy both the DLLs contained into the 120 source folder into both SQL Server 2014 x32 and x64 DTS paths, which means:

copy ".../desktop/120/*.dll" "C:\Program Files (x86)\Microsoft SQL Server\120\DTS\PipelineComponents"
copy ".../desktop/120/*.dll" "C:\Program Files\Microsoft SQL Server\120\DTS\PipelineComponents"

If at the installation time you customized the installation path of the MS SQL Server, you need to copy the DLL accordingly to that location. You can rely on the windows registry in order to spot where this path is. For more info look here

Registering the DLLs into the GAC.

The last step is to register the DLLs we have just copied into the Global Assembly Cache. To do so, we can either use the GACUTIL.EXE command line tool (shipped with Visual Studio) or use some GAC utilities, such as GacManager. If you are familiar with gacutil and with command lines tools, then use gacutils; otherwise if you prefer a GUI tool, use the GacManager procedure.

Procedure with GacUtil.exe

Run the VS2012 command prompt as administrator. If Visual Studio is installed on the system, a commodity shortcut should be present into the start menu (VS2012 x86 Native Tools Command Prompt). Once started as administrator, navigate to the same DLL folder source where you copied the DLL before. In our previous example it was "../desktop/120/". From there, execute the following commands:

gacutil /f /i Newtonsoft.json.dll
gacutil /f /i com.webkingsoft.JSONSource_120.dll

Check the output of every command and make sure the DLL installation go fine. Upon successful command execution, your should read a message similar to tje following:

Assembly successfully added to the cache

Congratulations! JSONSource is now installed and ready to be used.

Procedure with GacManager

Download and install GacManager utility from here.
Once installed, start it as administrator. Make sure you start that as administrator, otherwise the program will not work.
Once started, type "json" into the search box in the upper-right corner, so that we make sure there is no previous version installed. If you spot any previous DLL version of JSONSource or Newtonsoft.json, uninstall them.
At this point, you can proceed with the installation: pick and install first the Newtonsoft.json and then com.webkingsoft.JSONSource_XXX.dll, from the folder choosen in the previous step (DLL Copy). Please install each DLL at a time. This tools is nice, but seems to have problem with batch operations.
Once the DLLs are installed, reload the DLL list and perform the search by "json" again. If everything went ok, you should be able to see the new installed DLLs in the list!

Congratulation! JSONSource is now installed and ready to be used.


In order to see if the component is working, open visual studio and create a new SSIS project. Create an empty DataFlowTask and look into the SSIS ToolBox if there are those two components:
JSON Filter
JSON Source Component

Important notes for x32 and x64 environments

Microsoft Visual Studio only runs in 32 bit mode. This means that, if you only install the DLLs into the x64 folder, you would not be able to see the component into the Development environment. For this reason, in case you have the x64 version of MS SQL server, it is recommended to copy the DLLs both into the MSSQL Server X32 and X64 paths.
If so, you are now ready to use this component.

Reviews for this release

Amazing! You saved my a$$!!!! This is the first decent JSON Parser for SSIS that I've come across. Check your Paypal and CHEERS!!!!
by jmacfadyen on Sep 16, 2016 at 12:55 AM
Finally, a stable, production solution for getting JSON support into SSIS that doesn't cost an arm and a leg. Developer is very responsive as well, and will quickly fix any issues encountered.
by j0ksta on Jul 12, 2016 at 4:51 PM
I have tested the deserializing part of this tool. The parts are stable in use. Great work and finally some support for Json in SSIS!!
by eric6450 on Jun 19, 2016 at 6:17 AM
I've very pleased with JSON Source Component. I'm using it on SQL Server 2016 Enterprise to build a package that calls Qualtrics APIs to obtain survey response data. Part of that involves parsing a JSON reponse from the Qualtrics API, and JSON Source Component is perfect for that task. It is easy to work with as a developer, it was easy for our DBA to install the DLLs on the server, and it works in most cases. The only trouble I've run into is when attempting to use JSON Source Component in two separate Data Flow Tasks within a single package; otherwise I've had no trouble.
by ecklesweb on Jul 21, 2016 at 12:57 PM