Once you know the SSI Toolbox, it is time for configurations and parameters, and to convert a project.
Editor’s Note: This article is excerpted from chapter 3 of Extract, Transform, and Load with SQL Server Integration Services--with Microsoft SQL Server, Oracle, and IBM DB2, by Thomas Snyder and Vedish Shah.
Configurations and Parameters
Depending on the type of deployment model you choose, you can use either configuration files or parameters. The legacy model lets you create configuration files that are separate from your packages, whereas the default model lets you create parameters, project- or package-level, which are part of the entire project.
If you opt for the legacy model, you can simply right-click on the control flow window and select Package Configurations. Enable the configurations, name your file and location, pick your desired properties to use, name your config file, review the changes, and voilà: you have a config file! Config files are designated with a .dtsConfig extension. Any package, across any projects and across any solution, can share the same config file. However, the config file needs to be referenced first before it is accessed.
If you opt for the default model, you can create parameters, which are like configuration files but are located within the project or package. You can create parameters at two levels: package and project. Project parameters are created by double-clicking the project.params folder under the project name in the Solution Explorer. Package parameters are created by accessing the package’s Parameters view. Parameters in the package are only accessible to the package itself and no other packages. Parameters in the project are global and accessible by every package in the project.
Converting a Project
As we mentioned at the beginning of the chapter, the default model of a SSIS solution is the project deployment model. To convert it to the legacy package deployment model, right-click the project name and then click Convert to Package Deployment Model, as shown in Figure X.
Figure 1: Converting a project to the package deployment model
Once your project has been converted to the package deployment model, assuming there are no errors, you will be able to see the model type next to your project name, as shown in Figure xx.
Figure 2: A converted project
So, what does it take to convert your legacy project to a project deployment model? Well, doing so is very simple: you can just open your legacy solution using SSDT, and it will detect the discrepancies compared to the default model type and provide upgrade options. When you are converting a project to this model, you are technically taking all the packages and configuration files from the legacy model and putting them in an .ispac file: the deployment utility of the project deployment model. If your project was already built as a package deployment model within SSDT, then right-click the project name and click Convert to Project Deployment Model. The Integration Services Project Conversion Wizard will be displayed, as shown in Figure 3.
Figure 3: Converting to the project deployment model using Conversion Wizard
One important thing to note here is the verbiage on the first screen of the wizard. Since the conversion wizard was accessed from within SSDT, it will use the same project folders and overwrite the existing contents in that folder—thus, the warning to back up any important files before conversion. The Conversion Wizard, once you step through it, will also provide an option to convert any configuration files used into project parameters, as shown in Figure 4.
Figure 4: Project parameters
You can also access the Conversion Wizard directly from Windows Explorer for your desired SQL Server version: C:\Program Files (x86)\Microsoft SQL Server\130\DTS\Binn\ ISProjectWizard.exe.
The only difference is the way the Conversion Wizard handles the conversion (Figure 5).
Figure 5: Conversion Wizard, directly accessed
Next time: Database Setup. 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!
More 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.
TRY 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.
Forms 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.
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:
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.
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:
LATEST COMMENTS
MC Press Online