SSIS - Overview John Manguno

What will we be discussing today? Outline What will we be discussing today? Matrix Reports Individualized Letters with SubReports (Award Letters) DrillDown Reporting Updating Data with SSRS Charts, Maps, and other BI like features (Google API Geolocation Data) This session is more about demonstrating some of the possibilities of SSRS and less about how to actually accomplish those tasks, though we can certainly discuss any of these in more detail.

Outline

Project Deployment Model vs Legacy Package Deployment For all of the notes, go here: https://docs.microsoft.com/en-us/sql/integration-services/packages/deploy-integration-services-ssis-projects-and-packages?view=sql-server-2017 TL:DR Project deployment is the newer and more powerful way to write SSIS packages, and is what we will discuss in this session. It requires installation of the SSISDB. ** Cannot be installed on SQL Express All Integration Services objects are stored and managed on an instance of SQL Server in a database referred to as the SSISDB catalog. The catalog allows you to use folders to organize your projects and environments. Each instance of SQL Server can have one catalog. Each catalog can have zero or more folders.

I personally prefer to have separate Projects for discrete tasks, but you can also have a single Project with all of your packages. SSIS 2012 requires a full deploy every time, but SSIS 2016 allows for individual deployment.

Demo: Ice Cream SIS Integration Step 1 – create a Data Flow task to import CSV file to table. Step 2 – create a File System task to move file to archive. Step 3 – create a Data Flow task to create a csv file with SQL Query. Discuss deployment (SQLExpress does not support SSIS).