So far in this series I have shown how to create a custom connection manager and also how to create a user friendly interface to configure and test it. In this post I’m going to outline the steps I went through to create a custom source component for SSIS. By the end of this post I will show messages that are in a RabbitMQ queue being consumed by an SSIS package.

Following on from my introductory post, here I will be explaining how to develop a Custom Connection Manager for RabbitMQ. This connection manager will then be used in future posts by a custom Source and Destination component. What is a Connection Manager for? From the MSDN documentation: “Integration Services uses connection managers to encapsulate the information needed to connect to an external data source. […] If the connection managers and external data sources supported by Integration Services do not entirely meet your requirements, you can create a custom connection manager.

In my previous post I explained how to create a custom connection manager for SSIS to connect to RabbitMQ. In this post I’m going to extend this further by adding a custom UI where the connection can be configured and tested. Preparing the Project The first step is to add a few more references: Microsoft.SqlServer.Dts.Design Microsoft.SqlServer.DTSPipelineWrap Microsoft.SqlServer.DTSRuntimeWrap Microsoft.SqlServer.PipelineHost These assemblies can be found in C:\Program Files (x86)\Microsoft SQL Server\110\SDK\Assemblies The next step is to add two new files, the first is an empty class file which I’ve called RabbitMQConnectionManagerUI.

Introduction I’ve been using SSIS for a long time and have always been curious about developing custom sources and destinations. After having a bit of a look through the MDSN documentation (http://msdn.microsoft.com/en-us/library/ms345161.aspx) last night I thought I would give it a go. So over the next couple of blog posts I’m going to attempt to create a custom Connection Manager, Source and Destination for RabbitMQ. RabbitMQ is a widely used message broker built on the Advanced Message Queuing Protocol (AMQP).

In this post I will outline a very simple approach to creating a report template for your SSRS solution. Getting Started Create a new (or open an existing) reporting solution and add a new report, let’s call it _Template.rdl - this report will form the basis of our template. Open this report and add any standard formatting or style that you want for all future reports. Maybe you have standard header/footers, e.

In this post I’ll outline how I used a project from Codeplex http://unittestssrs.codeplex.com to write tests against SSRS reports. From the description from the project page: Allows testing reports deployed to reporting server 2008R2 or 2012 in Native or SharePoint mode. The tests cases are created in xml file in declarative form. Getting Started 1. Download and extract the latest release from the Codeplex site http://unittestssrs.codeplex.com 2. Open the Settings.xml file, in here you will need to set a few different options: