02
Sat, Nov
2 New Articles

TechTip: Data Source Base Project, Part 3 - SSIS Code Structure

Typography
  • Smaller Small Medium Big Bigger
  • Default Helvetica Segoe Georgia Times

In Part 3 we look at creating our data source SSIS code structure.  Click here to review Part 1 and Part 2

Editor’s Note: This article is excerpted from chapter 5 of Extract, Transform, and Load with SQL Server Integration Services--with Microsoft SQL Server, Oracle, and IBM DB2, by Thomas Snyder and Vedish Shah.

As our final step, we will prepare our package for reuse by copying the package to a location external to our SSIS solution.

For readers who may not be familiar with Visual Studio, I would like to do a quick review of the structure of the source code in a solution that will help you understand how we will prepare our package for reuse.

In Windows File Explorer, if you navigate to the location of your project, you will see the parent SSISBaseProject folder with a child SSISBaseProject folder (Figure 5.17).

TechTip: Data Source Base Project, Part 3 - Figure 1

Figure 17: Visual Studio source code structure

In the parent folder, there is a single file: SSISBaseProject.sln. In the child folder, there are five files:

  • dtsx
  • params
  • database
  • dtproj
  • dtproj.user

The .sln file is the solution file that Visual Studio uses to define the entire structure of the code used within Visual Studio, which could contain multiple projects.

The .dtsx file is the package file, which is what we will use as the base package for the rest of the projects. This file contains the SSIS code that we have set up so far. This will be the only file that we need to copy for the rest of our projects.

When you add a new or an existing Integration Services project to a solution, SQL Server Data Tools (SSDT) creates the miscellaneous project files.

  • The *.dtproj file contains information about project configurations and items such as packages.
  • The *.dtproj.user file contains information about your preferences for working with the project.
  • The *.database file contains information that SSDT requires to open the Integration Services project.

Preparing for Reuse

In Windows File Explorer, navigate to a location that you would like to use for your future projects and create a new folder called BaseProject or whatever you’d like. This folder is where we will store our project.dtsx file, which we will rename to BaseProject.dtsx.

Open the SSISBaseProject in Visual Studio. Then select File > Save Copy of Package.dtsx As…. (Figure 5.18, part 2). Next select the target folder location that we created previously and specify the name as BaseProject.

TechTip: Data Source Base Project, Part 3 - Figure 2

Figure 5.18: Visual Studio: Save Copy

The result should be that we created a new file called BasePackage.dtsx within the newly created BaseProject folder. The preparation steps simply copied the package.dtsx file from your project folder into a different location, with the only difference being in the VersionGUID. This copied file will be much cleaner to use in future projects because we removed it from all the miscellaneous solution files that we will not be using.

Copy the Base Project

In the following chapters, we will start our SSIS development by creating a new SSIS project that will import the base package. These steps will be repeated as the first step in most of the following chapters.

  1. Open Visual
  2. Select File > New Project….
  3. Select Templates > Business Intelligence > Integration Services Project.
  4. Enter the name for your project and select the directory location to be

Once the new project is created, we will delete the default SSIS project and import the base project, as shown at the right side of the screen in Figure 5.19.

TechTip: Data Source Base Project, Part 3 - Figure 3

Figure 5.19: Deleting the default project package

Now that we have deleted the default package, we will now add the base package (Figure 5.20).

TechTip: Data Source Base Project, Part 3 - Figure 4

Figure 5.20: Adding an existing SSIS package

After opting to add the existing package, you will be presented with a screen (Figure 5.21) to select the location of the base package.

TechTip: Data Source Base Project, Part 3 - Figure 5

Figure 5.21: Selecting an existing SSIS package

Once you click OK after you selected the base project, you will see BasePackage.dtsx under the SSIS Packages in the Solution Explorer (Figure 5.22). This process copied the base package into your new SSIS solution.

TechTip: Data Source Base Project, Part 3 - Figure 6

Figure 5.22: New SSIS package created from the base package

We now have a new project, ready to go, which contains all the connection managers configured in the base project. If you double-click on the BasePackage.dtsx file you just added, it will open the project and you can see that your connection managers are now available for usage.

Creating a Package Template

The previous steps to copy the base project are completely legitimate, but to take it all the way home, let’s make a package template out of our base project. By creating a package template, you will be able to select your template from the new item menu.

To do this is simple enough: we will simply copy our base package into the SSIS package template folder. But before we do that, let’s rename our template to a user-friendly name (MCPress Database Agnostic Base.dtsx), as that will be what is displayed when you select it (Figure 5.23).

TechTip: Data Source Base Project, Part 3 - Figure 7

Figure 5.23: Renaming the base template package

TechTip: Data Source Base Project, Part 3 - Note

Then copy our base template package into the SSIS package template:

C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\PrivateAssemblies\ProjectItems\DataTransformation Project\DataTransformationItems

When you initially create your new SSIS packages, the default package will be blank and can’t be changed. So simply create a new SSIS project as you normally would to start with your empty project (Figure 5.24).

TechTip: Data Source Base Project, Part 3 - Figure 9

Figure 5.24: Creating a new SSIS project to add a package template

Once the new project is created, right-click on your project in Solution Explorer, select Add, then New item….

You will now be able to see your custom package template available as an item to add, as shown in Figure 5.25.

TechTip: Data Source Base Project, Part 3 - Figure 10

Figure 5.25: Selecting your new custom package template

Once you’ve added your package template, you could delete the original project.dtsx and rename the MCPress Database Agnostic Base1.dtsx to match your project. Please note that when you add the package template, it actually copies the .dtsx file into your project, which means that you could update the package without impacting your reusable base package in the Visual Studio SSIS Package location.

I think this is convenient and will make life easier for us in the following chapters, to take advantage of reusing our connection manager efforts in this chapter.

However, if I wanted to be picky, I would have liked to have our custom package template available from the initial creation template menu. It also seems hacky when you manually place files in directories when you’re dealing with a Microsoft windows graphic-intensive tool without an import option for these templates, but that could possibly be a little enhancement in a future release.

Look for more tips from Tom's book in an upcoming issue of MC TNT. Can't wait?  Pick up your copy of Tom's book, Extract, Transform, and Load with SQL Server Integration Services at the MC Press Bookstore Today!

 

Thomas Snyder

Thomas Snyder has a diverse spectrum of programming experience encompassing IBM technologies, open source, Apple, and Microsoft and using these technologies with applications on the server, on the web, or on mobile devices.

Tom has more than 20 years' experience as a software developer in various environments, primarily in RPG, Java, C#, and PHP. He holds certifications in Java from Sun and PHP from Zend. Prior to software development, Tom worked as a hardware engineer at Intel. He is a proud United States Naval Veteran Submariner who served aboard the USS Whale SSN638 submarine.

Tom is the bestselling author of Advanced, Integrated RPG, which covers the latest programming techniques for RPG ILE and Java to use open-source technologies. His latest book, co-written with Vedish Shah, is Extract, Transform, and Load with SQL Server Integration Services.

Originally from and currently residing in Scranton, Pennsylvania, Tom is currently involved in a mobile application startup company, JoltRabbit LLC.


MC Press books written by Thomas Snyder available now on the MC Press Bookstore.

Advanced, Integrated RPG Advanced, Integrated RPG
See how to take advantage of the latest technologies from within existing RPG applications.
List Price $79.95

Now On Sale

Extract, Transform, and Load with SQL Server Integration Services Extract, Transform, and Load with SQL Server Integration Services
Learn how to implement Microsoft’s SQL Server Integration Services for business applications.
List Price $79.95

Now On Sale

BLOG COMMENTS POWERED BY DISQUS

LATEST COMMENTS

Support MC Press Online

$

Book Reviews

Resource Center

  • SB Profound WC 5536 Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application. You can find Part 1 here. In Part 2 of our free Node.js Webinar Series, Brian May teaches you the different tooling options available for writing code, debugging, and using Git for version control. Brian will briefly discuss the different tools available, and demonstrate his preferred setup for Node development on IBM i or any platform. Attend this webinar to learn:

  • SB Profound WP 5539More than ever, there is a demand for IT to deliver innovation. Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects. The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the company are not aligned with the current IT environment.

  • SB HelpSystems ROBOT Generic IBM announced the E1080 servers using the latest Power10 processor in September 2021. The most powerful processor from IBM to date, Power10 is designed to handle the demands of doing business in today’s high-tech atmosphere, including running cloud applications, supporting big data, and managing AI workloads. But what does Power10 mean for your data center? In this recorded webinar, IBMers Dan Sundt and Dylan Boday join IBM Power Champion Tom Huntington for a discussion on why Power10 technology is the right strategic investment if you run IBM i, AIX, or Linux. In this action-packed hour, Tom will share trends from the IBM i and AIX user communities while Dan and Dylan dive into the tech specs for key hardware, including:

  • Magic MarkTRY the one package that solves all your document design and printing challenges on all your platforms. Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product. Make sure your data survives when catastrophe hits. Request your trial now!  Request Now.

  • SB HelpSystems ROBOT GenericForms of ransomware has been around for over 30 years, and with more and more organizations suffering attacks each year, it continues to endure. What has made ransomware such a durable threat and what is the best way to combat it? In order to prevent ransomware, organizations must first understand how it works.

  • SB HelpSystems ROBOT GenericIT security is a top priority for businesses around the world, but most IBM i pros don’t know where to begin—and most cybersecurity experts don’t know IBM i. In this session, Robin Tatam explores the business impact of lax IBM i security, the top vulnerabilities putting IBM i at risk, and the steps you can take to protect your organization. If you’re looking to avoid unexpected downtime or corrupted data, you don’t want to miss this session.

  • SB HelpSystems ROBOT GenericCan you trust all of your users all of the time? A typical end user receives 16 malicious emails each month, but only 17 percent of these phishing campaigns are reported to IT. Once an attack is underway, most organizations won’t discover the breach until six months later. A staggering amount of damage can occur in that time. Despite these risks, 93 percent of organizations are leaving their IBM i systems vulnerable to cybercrime. In this on-demand webinar, IBM i security experts Robin Tatam and Sandi Moore will reveal:

  • FORTRA Disaster protection is vital to every business. Yet, it often consists of patched together procedures that are prone to error. From automatic backups to data encryption to media management, Robot automates the routine (yet often complex) tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:

  • FORTRAManaging messages on your IBM i can be more than a full-time job if you have to do it manually. Messages need a response and resources must be monitored—often over multiple systems and across platforms. How can you be sure you won’t miss important system events? Automate your message center with the Robot Message Management Solution. Key features include:

  • FORTRAThe thought of printing, distributing, and storing iSeries reports manually may reduce you to tears. Paper and labor costs associated with report generation can spiral out of control. Mountains of paper threaten to swamp your files. Robot automates report bursting, distribution, bundling, and archiving, and offers secure, selective online report viewing. Manage your reports with the Robot Report Management Solution. Key features include:

  • FORTRAFor over 30 years, Robot has been a leader in systems management for IBM i. With batch job creation and scheduling at its core, the Robot Job Scheduling Solution reduces the opportunity for human error and helps you maintain service levels, automating even the biggest, most complex runbooks. Manage your job schedule with the Robot Job Scheduling Solution. Key features include:

  • LANSA Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.

  • LANSAWhen it comes to creating your business applications, there are hundreds of coding platforms and programming languages to choose from. These options range from very complex traditional programming languages to Low-Code platforms where sometimes no traditional coding experience is needed. Download our whitepaper, The Power of Writing Code in a Low-Code Solution, and:

  • LANSASupply Chain is becoming increasingly complex and unpredictable. From raw materials for manufacturing to food supply chains, the journey from source to production to delivery to consumers is marred with inefficiencies, manual processes, shortages, recalls, counterfeits, and scandals. In this webinar, we discuss how:

  • The MC Resource Centers bring you the widest selection of white papers, trial software, and on-demand webcasts for you to choose from. >> Review the list of White Papers, Trial Software or On-Demand Webcast at the MC Press Resource Center. >> Add the items to yru Cart and complet he checkout process and submit

  • Profound Logic Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application.

  • SB Profound WC 5536Join us for this hour-long webcast that will explore:

  • Fortra IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn: