Deploy SSIS packages by using the deployment utility, SQL Server, and file systems

-
For project deployment, you must ensure that all the related objects needed for the package execution are also part of the package. For example, when a Connection Manager is created, it is specific for the package within which it was created, unless it is promoted to a project-level Connection Manager by right-clicking it and selecting Convert To Project Connection.












Similarly, any parameter that you want to be included at the project level, such as, Server-Name, DatabaseName, FolderName, etc. can be created at the project level so it only needs to be changed in one place and will be available for all the packages in the project. And once the project has been deployed to a different server, for example to the Development, QA, or Production server, the parameter value only needs to be changed in one place.

The Project.params tab opened with project parameters, and also under Connection Managers, you see the project level connections.






The project deployment options are:
  • Deploy packages directly to server using a wizard
  • Create an ISPAC file using a wizard; deployment can be handed off to be done by an administrator

The start the project deployment, right-click the project name and select Deploy to open the Integration Services Deployment Wizard. On the Select Destination page, enter the Server Name and Path from the SSISDB Catalog; you can create a new project folder in the SSISDB Catalog by selecting New Folder. Now press the Deploy button to have the packages deployed to the selected SSISDB project folder. You see the newly deployed packages under the Integration Services Catalog folder > SSISDB Catalog > Project Name.












If you deploy a project multiple times to the same SSISDB catalog, you are able to see all the versions, including the Current version when you right-click the project name under the Projects folder and select Versions. The Project Versions window displays. The current version has the check box selected. If you ever need to rollback, just highlight the row for the version you want to revert to and press the button Restore To Selected Version.












If you need to see the deployment folder for the project, simply right-click the project and select Properties and select the Deployment on the left pane. Here you see the Server Name and the Server Project Path for this project.








Comments

Post a Comment

Popular Posts

Install Master Data Services (MDS)

-
Image
The installation of Master Data Services consists of three steps as follows: 1. Install required Windows roles and features 2. Install Master Data Services from the SQL Server installation media 3. Configure Master Data Services from the MDS Configuration Manager Windows roles and features installation To install the Windows roles and features required for MDS, you can use Windows Server Manager  or through a PowerShell script. To start the Windows roles and features installation using  Windows Server Manager follow these steps: 1. Open Server Manager and click on Manage on the menu bar, then click Add Roles and  Features from the drop-down menu options to launch the Add Roles and Features  Wizard. 2. On the Select installation type window, select the “Role-based or feature-based installation”  option as shown and click Next. 3. On the Select destination server window, click the checkbox for the “Select a server  from the server pool” optio
Read more

Non-blocking, semi-blocking, and blocking transforms in SSIS

-
Not all Data Flow transforms are created equal. In fact, some are much faster and require a  lot less memory (non-blocking transforms). Others are slower while consuming much more  memory (blocking transforms), and some are in between (semi-blocking transforms). We don’t  always have a choice if we need to use a certain transform to do a certain specified task, but  it is good to know the differences between these types of transforms so that we can better  understand performance and resource utilization issues. Synchronous and asynchronous There is another related aspect about Data Flow transforms, which is their ability to quickly  process a row as they are coming into the transform, independently of any other rows that  came before or after (synchronous transforms). The other type of transform needs to be  dependent on some or all of the rows that come before and after (asynchronous transforms). On the whole, non-blocking transforms are also synchronous, thus are fast and
Read more

Design an appropriate storage solution, including hardware, disk, and file layout

-
Image
The data warehouse storage’s performance can be measured by  analyzing the time it takes for read and write operations to complete, known as latency , and by  analyzing how much data volume it can read or write in each time frame, known as throughput .  High latency and low throughput can be an indication of an improper selection for the  storage infrastructure or incorrect hardware and software configurations. Performance of a storage subsystem can  be estimated based on several criteria: Volume of data Rate of change and growth of the data Data retention policy Number of concurrent users Typical workloads expected Two important metrics associated with storage are throughput and Input/Output Per  Second (IOPS) . Throughput is a measure of the amount of data that can be transferred in a  period. This is typically measured in megabytes or gigabytes per second. IOPS is the number of  I/O read or write operations that can complete in a second.  It is important
Read more