The post “Are we heading towards recession again?” is mainly intended for SQL Developers and DBA’s. Global economy growth sustainability, corporate targets, investments, stock market, oil price, unemployment, dollar value and major Bank balance sheets may decide the recession. Since we are not the financial experts we really can’t get into this stuff but Information Technology is the top industry to have a huge impact if recession hits. From the technology point we can clearly observe that there are major changes has been taken place and it has a direct impact on employment:
- “Cloud computing”
- “Artificial Intelligence”
Q. “Are we heading towards recession again?”
Yes!!! If you are not ready for the “CHANGE”
No!!! If you are capable to addict the “CHANGE”
Q. How to stop the recession?
You really can’t stop the financial crisis but you can handle it with the persistent preparation. As per the financial market analysts economic downturn might hit the recession but it might be mild one not like in 2007. There is no clear pattern that can exactly predict the recession and how long it will be but we have enough resources available to face the crisis.
Q. How can I get ready for the change?
This post helps you to understand the “Project deployment model in SSIS”. We have already created a SSIS package and environment is ready to deploy. Here are the ETL requirement and package details. We are going to deploy the package into SQL Server 2016 instance and use the same package to run for QA, TEST and PROD environment.
Source – Flat Files
We have created three different folders and customer flat files for DEV, QA and PROD as below:
This post can help you to understand the “Designing a simple SSIS package using SQL Server 2016” and SSIS Project Deployment Model in SQL Server 2016. Project Deployment Model is introduced in SQL Server 2012 and provides more flexibility in deploying, monitoring and maintaining SSIS packages. Here in this post we’ll take a simple example and see how to deploy SSIS package and use a single SSIS package for multiple environments. For implementation we used:
- SQL Server Data Tools 2015
- SQL Server 2016 Database
- SQL Server Management Studio 2017
We are going to design and deploy a SSIS package for a simple ETL requirement. We have a customer table and we’ll get the customer data feed as a flat file on daily basis. We just need to design a SSIS package that should fetch extract data from flat file and insert into customer table by following the below given conditions. To simplify the requirement this is not an incremental load instead we get only the new customer information. Here are the rules:
- SSIS package should be deployed on dedicated SSIS SQL Server 2016 instance
- We should be able to change the Flat File Path, SQL Server Instance Name, User Name, Password, and Database Name. It means we should be able to provide these values at runtime.
- The same package hosted on dedicated instance should be used for all 3 environments (Development, QA and Production)
- Customer table has to be truncated before loading data
We are going to design a simple ETL package and deploy using Project Deployment model. Here are the details:
||Flat File – Customer Information
||SQL Server – 3 Environments
Creating Integration Services Catalogs:
Before SQL Server 2012 we used to store SSIS packages either in MSDB or in physical file and parameters and configurations in XML file or in SQL Server table. But from 2012 game is changed and now we have “Integration Service Catalogs” introduced. By default there are no catalogues created and we have to create a new catalog and it automatically creates “SSISDB”. All SSIS packages and configurations, parameters are stored in SSISDB. Here is a good article that explains how to create a SSIS catalog. I have created SSIS catalog and added a new folder called XYZ_Product