I’ve been making smaller, more incremental changes to SSIS Catalog Browser – a free utility from the Data Integration Lifecycle Management suite (DILM Suite).
You can use SSIS Catalog Browser to view SSIS Catalog contents on a unified surface. Catalog Browser works with SSIS Catalogs on-premises and Azure Data Factory SSIS Integration Runtime, or Azure SSIS. It’s pretty cool and the price ($0 USD) is right!
The latest change is a version check that offers to send you to the page to download an update. You will find this change starting with version 0.7.7.0. Version 0.7.8.0 includes a slightly better-formatted version-check message. As I said, smaller, more incremental changes.
It’s free. That makes it difficult to beat the cost.
SSIS Catalog Browser is designed to surface all SSIS Catalog artifacts and properties in a single view. “What exactly does that mean, Andy?” You’re sharp. Let’s talk about why the surface-single-view is important.
Before I go on, you may read what I’m about to write here and in the companion post and think, “Andy doesn’t like the Integration Services Catalogs node in SSMS.” That is not accurate. I do like the Integration Services Catalogs node in SSMS. It surfaces enough information for the primary target user of SSMS – the Database Administrator – to see what they need to see to do their job, without “cluttering up” their interface with stuff that they rarely need to see and even more-rarely change.
In the companion post I shared this image of the windows (and pages) you need to open in SSMS to view the configured execution-time value of a parameter that is mapped via reference:
That’s a lot of open windows.
So how does one view the same configuration metadata in SSIS Catalog Browser?
Under the Project node (LiftAndShift), we find a virtual folder that holds Project Parameters.
In Project parameters, we find a reference mapping – indicated by underlined text decoration and describing the reference mapping as between the parameter (ProjectParameter) and the SSIS Catalog Environment Variable (StringParameter).
Expanding the reference mapping node surfaces References. There are two references named env1 and env2. Since references can reference SSIS Catalog Environments in other Catalog folders, the fully-qualified path to each SSIS Catalog environment is shown in folder/environment format.
Expanding each reference node surfaces the value of the SSIS Catalog Environment Variable in each SSIS Catalog Environment.
I call this feature Values Everywhere, and I like it. A lot.
Values Everywhere From the Project Reference Perspective
Values Everywhere is perspective-aware. Whereas from the perspective of an SSIS Project Parameter, Values Everywhere surfaces the reference mapping in the format parameter–>environment variable, in the Project References virtual folder, Values Everywhere surfaces the same relationship as environment variable–>parameter:
Values Everywhere perspectives follow intuition when surfacing reference mapping relationships. (Did I mention I like this feature? A lot?)
SSIS Catalog Browser provides a clean interface for enterprise Release Management and Configuration teams. And it’s free.
I can hear you thinking, “Why is Catalog Browser free, Andy?” I give away Catalog Browser to demonstrate the surfacing capabilities of SSIS Catalog Compare.
SSIS Catalog Compare
SSIS Catalog Compare not only surfaces two SSIS Catalogs side by side, you can compare the contents of the Catalogs:
You can also script an entire SSIS Catalog which produces T-SQL script and ISPAC files for every artifact in the SSIS Catalog (organized by instance and folder):
You can also deploy all artifacts contained in an SSIS Catalog Folder from one SSIS Catalog to another:
This functionality is an efficient method for Data Integration Lifecycle Management – or DevOps – with SSIS.
SSIS Catalog Compare even works with Azure Data Factory SSIS Integration Runtime, so you can use SSIS Catalog Compare to lift and shift SSIS from on-premises Catalogs to the cloud.
This is the first time I am delivering this session. It still has that new presentation smell!
Azure Data Factory – ADF – is a cloud data engineering solution. ADF version 2 sports a snappy web GUI (graphical user interface) and supports the SSIS Integration Runtime (IR) – or “SSIS in the Cloud.”
Attend this session to learn: – How to build a “native ADF” pipeline; – How to lift and shift SSIS to the Azure Data Factory integration Runtime; and – ADF Design Patterns to execute and monitor pipelines and packages.
SSIS Framework Community Edition is free and open source. You may know can use SSIS Framework Community Edition to execute a collection of SSIS packages using a call to a single stored procedure passing a single parameter. But did you know you can also use it to execute a collection of SSIS packages in Azure Data Factory SSIS Integration Runtime? You can!
In this free webinar, Andy discusses and demonstrates SSIS Framework Community Edition – on-premises and in the cloud.
Join SSIS author, BimlHero, consultant, trainer, and blogger Andy Leonard at noon EDT Thursday 20 Sep 2018 as he demonstrates using Biml to make an on-premises copy of an Azure SQL DB.
I demonstrate a cool SSIS Catalog Browser feature that helps ADF developers configure the Execute SSIS Package activity.
To see it in action, download SSIS Catalog Browser – it’s one of the free utilities available at DILM Suite. Connect to the instance of Azure SQL DB that hosts an Azure Data Factory SSIS Integration Runtime Catalog, select the SSIS Package you desire to execute using the Execute SSIS Package activity, and then copy the Catalog Path from the Catalog Browser status message:
Paste that value into the Package Path property of the Execute SSIS Package activity:
You can rinse and repeat – Catalog Browser surfaces Environment paths as well:
I am excited to announce a brand new course (it still has that new course smell) from Brent Ozar Unlimited and honored to deliver it! This one-day, live, online course is titled Fundamentals of Azure Data Factory and it’s designed to introduce you to Azure Data Factory (ADF).
There will be demos. Live demos. Lots of live demos!
Azure Data Factory, or ADF, is an Azure PaaS (Platform-as-a-Service) that provides hybrid data integration at global scale. Use ADF to build fully managed ETL in the cloud – including SSIS. Join Andy Leonard – author, blogger, and Chief Data Engineer at Enterprise Data & Analytics – as he demonstrates practical Azure Data Factory use cases.
In this course, you’ll learn:
The essentials of Azure Data Factory (ADF)
Developing, testing, scheduling, monitoring, and managing ADF pipelines
Lifting and shifting SSIS to ADF SSIS Integration Runtime (Azure-SSIS)
ADF design patterns
Data Integration Lifecycle Management (DILM) for the cloud and hybrid data integration scenarios
To know if you’re ready for this class, look for “yes” answers to these questions:
Do you want to learn more about cloud data integration in Azure Data Factory?
Is your enterprise planning to migrate its data, databases, data warehouse(s), or some of them, to the cloud?
In May, Microsoft announced the general availability of Azure Data Factory SSIS Integration Runtime. Customers immediately began deploying SSIS from on-premises servers to the cloud. Some quickly recognized some gaps in the process, such as:
On-premises, enterprises have the option of executing SSIS from the file system or an SSIS Catalog (or the MSDB database). The only option available in Azure at the time of this writing is execution from the SSIS Catalog.
The DevOps story for the SSIS Catalog is… challenging. If enterprises use Catalog Environments and References, for example, developers have to devise a method to extract environment and reference metadata from the SSISDB database. Opening an environment and clicking the Script button results in an empty script window in SSMS. (Developers don’t even get an empty window when they click the Script button for Reference configurations…).
The Empty Script Window…
SSIS Catalog Compare, by comparison, migrates the entire SSIS Catalog configuration between catalogs.
To support DevOps for SSIS – on-premises, in ADF SSIS Integration Runtime, or hybrid scenarios – SSIS Catalog Compare facilitates scripting Catalog Folders and all contents (and also entire Catalogs!):
The scripts are numbered in dependency-order. Most artifacts – everything except the actual ISPAC file, in fact – are T-SQL scripts. I love this because it removes a bunch of the “mystery” for Production DBAs who may be deploying the SSIS solution.
Sensitive parameters – like connection passwords – are not exported. The person performing the deployment needs to supply sensitive parameter values stored in either SSIS Catalog Environments or in Parameter literal overrides. Both appear as shown here (click to enlarge):
Similarly, when using SSIS Catalog Compare to deploy between catalogs, sensitive values are not transferred. If you watch the gif at the top of this post, you notice the last step is to update the Sensitive Environment Variable value used to override the connection manager Password property. Sensitive values must be updated post-deployment and SSIS Catalog Compare allows deployment personnel to perform these updates.
SSIS Catalog Compare version 3 is designed to support on-premises, cloud, and hybrid data engineering / integration DevOps for enterprises. Take a look and let me know what you think!
I wrote a book about practicing Data Integration Lifecycle Management with SSIS. In the book I explore tools I built to support DevOps with SSIS. Collectively, I call them the Data Integration Lifecycle Management Suite (DILM Suite). Many utilities at DILM Suite are free and some are open-source:
The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.