SSIS – SQL Server Integration Services Connection Manager Tips and Tricks

Connection Managers and Package Configurations are among the most critical components of SQL Server Integration Services (SSIS) Packages. It is very essential to have a thorough understanding of these components while working with SSIS.

In this post, we will see following tips and tricks related to Connection Managers and Package Configurations:

• Adding an “Application Name” property to the connection string
• Creating Two Connection Managers for each Database Connection
• Capturing Connection Manager details in Package Configurations

To continue reading, catch the full article here: SQL Server Integration Services Connection Manager Tips and Tricks.

• SSIS – Quickest way to add an existing SSIS Package to a Project
• SSIS – Update Properties of Multiple Tasks in One-Go
• SSIS – Define you own Keyboard Shortcuts in SSIS Package Designer
• SSIS – Ensure Consistency across Packages using Template Packages

SQL Server 2012 – Ability to Replicate Environments and Copy Variables Across Environments in SSIS Catalog

Most of you who are aware of SSIS Enhancements in SQL Server 2012, might already be knowing that in the Deployment Model, we can now create something called as an Environment (say one for each like Dev, Test etc.) in SSMS and add variables to each of the environment to hold the configurable values for each of the environments. I noticed that, we need to create the variables for each of the environments separately even if all the environments are using the same set of variables, which is a duplication of effort and a tedious job if number of variables is huge.

As part of this observation, I have submitted a feedback to Microsoft on the Microsoft Connect site. Below is a snapshot of the feedback. If you want to see this feature in future updates (May be in Service Packs), please vote for this feedback by clicking on the link below the screenshot.

SSIS 2012 – Ability to Replicate Environments and Copy Variables Across Environments in Catalog

I am in the process of writing my next post on the Learning Resources for SSIS Enhancements in SQL Server 2012 as part of the SQL Server 2012 Enhancements Learning Resources series.

Related articles

• SQL Server 2012 – Transact-SQL Enhancements – Learning Resources
• SQL Server 2012 – Data Quality Services (DQS) – Learning Resources
• SQL Server 2012 – High Availability Enhancements – Learning Resources
• Tips ‘N’ Tricks – SSIS – Ensure Consistency across Packages using Template Packages
• Tips ‘N’ Tricks – SSIS – Define you own Keyboard Shortcuts in SSIS Package Designer
• Tips ‘N’ Tricks – SSIS – Update Properties of Multiple Tasks in One-Go
• Tips ‘N’ Tricks – SSIS – Quickest way to add an existing SSIS Package to a Project

Tips ‘N’ Tricks – SSIS – Quickest way to add an existing SSIS Package to a Project

We often add one or more existing SSIS Packages to an Integration Services Project in SQL Server Business Intelligence Development Studio (BIDS). And like many other scenarios, in this scenario also there are two approaches to perform this action. Let’s take a look at both the approaches in this tip.

 

Regular Approach (5 Steps)

1. Right click on the SSIS Packages folder in the Integration Services Project in BIDS and Select Add Existing Package from the context menu.
2. In the Add Copy of Existing Package dialog box select Package location as File System from the dropdown.
3. Click on the ellipsis button next to the Package path textbox.
4. Locate the SSIS package (.dtsx file) which you want to add from the file system.
5. Click OK in the Add Copy of Existing Package dialog box to finish adding the package.

Shortcut Approach (4 Steps)

1. Locate the SSIS package (.dtsx file) which you want to add from the file system.
2. Right click on the SSIS package in the file system and select Copy from the context menu (or alternately, select the Package and press Ctrl+C to copy the package).
3. Right click on the SSIS Packages folder in the Integration Services Project in BIDS.
4. Select Paste from the context menu to finish adding the package.

Note: This has been tested with BIDS 2008/2008 R2.

Reference: http://dattatreysindol.blogspot.in/2010/11/adding-ssis-package-to-project-hard.html

 

Take a look at the other Tips and Tricks in this Series on Tips, Tricks, Techniques, and Shortcuts to Improve Productivity, and Design and Coding Skills.