Traditionally, migrating SSIS Catalog, especially when dealing with encrypted sensitive data, could be a complex affair. One of the major hurdles was the perceived need to know the SSISDB encryption key from the source server. This key is crucial for decrypting sensitive data stored within the catalog. If this key was lost, unknown, or not easily accessible, the SSIS Catalog migration process could become a nightmare, often leading to manual reconfiguration or even data loss.

This is where tools like the SSIS Catalog Migration Wizard truly shine, revolutionizing how we approach SSIS Catalog migrations, particularly concerning sensitive data and environment-specific configurations.

SSIS Catalog Migration Wizard: A Secure and Streamlined Solution for SSIS Data

The SSIS Catalog Migration Wizard is a powerful and user-friendly tool designed to simplify the process of moving your SSIS Catalog between SQL Server instances. Its most significant advantage when it comes to sensitive data is its ability to handle encrypted information without requiring the user to possess the SSISDB encryption key from the source server. Beyond sensitive data, it offers critical features for managing environment and parameter values during the transfer.

How it addresses sensitive data and configuration concerns during SSIS migration:

• No SSISDB Encryption Key Required: This is the paramount feature. The Wizard intelligently extracts the necessary components, including encrypted sensitive data, from the source SSISDB and correctly re-encrypts them on the destination SSISDB using the destination’s encryption key. This means you don’t need to go through the arduous process of retrieving, backing up, or restoring the source SSISDB encryption key. This drastically reduces the risk of exposing sensitive data and simplifies the SSIS Catalog migration significantly.
• Seamless Re-encryption: The Wizard handles the decryption and re-encryption process behind the scenes. When an SSIS package with sensitive data is migrated, the Wizard ensures that this data is correctly encrypted with the destination server’s SSISDB encryption key, maintaining the integrity and security of your sensitive information.
• Replace Environment Variable and Parameter Values: A significant pain point in manual migrations is updating countless environment variables and parameter values to match the new environment. The SSIS Catalog Migration Wizard offers the crucial capability to define and replace these values during the migration process itself. This means you can proactively map old server names, database names, file paths, or other environment-specific settings to their new counterparts.
• Reduced Manual Intervention: By automating the handling of sensitive data and providing the ability to replace environment-specific values, the Wizard minimizes the need for manual intervention post-migration. This reduces the chances of human error that could lead to data exposure, corruption, or broken package execution. You won’t have to manually update connection strings, package parameters, or environment variables one by one, saving significant time and effort in SSIS data migration and configuration.
• Comprehensive Migration: Beyond sensitive data and configurable parameters, the Wizard migrates your entire SSIS Catalog structure, including projects, environments, references, etc. This ensures a consistent and complete transfer of your SSIS deployment.

Proactive Strategies for Seamless Variable and Parameter Value Replacement

To leverage the Wizard’s capability for variable and parameter value replacement effectively, consider SCMW’s proactive suggestions:

• Simplified Updating: The wizard streamlines the process of updating environment variables and parameter values to match the target environment during migration.
• Configurable Key-Value Pairs: Users can set up specific key-value pairs to replace existing values in both environment variables and SSIS project/package parameters.
• Intelligent Suggestions: The wizard features a “Suggest” button that provides recommendations for replacements based on the chosen “Replace Scope,” aiding users in configuring the correct values.
• Detailed Review: Users can review the specific environment variables and parameters that will be affected by clicking on the “Ref” column, which displays detailed mappings, ensuring accuracy and control over the migration process.

This functionality ensures that SSIS packages and projects are correctly configured for the new environment without manual intervention, saving time and reducing potential errors.

Best Practices for a Secure SSIS Catalog Migration

While the SSIS Catalog Migration Wizard significantly simplifies the process, it’s still crucial to adhere to best practices for a truly secure migration:

1. Plan Thoroughly: Before initiating any migration, have a clear plan. Identify all projects, environments, sensitive data, and environment-specific configurations involved.
2. Backup Everything: Always perform full backups of both the source and destination SSISDB databases before starting the migration. This provides a rollback point in case of any unforeseen issues. You can consider backing us SSISDB to .scmv file using SSIS Catalog Migration Wizard.
3. Test in a Non-Production Environment: If possible, perform a test migration to a non-production environment first. This allows you to identify and resolve any potential issues, including incorrect parameter replacements, before impacting your production systems.
4. Validate Post-Migration: After the migration is complete, thoroughly validate that all packages and connections are functioning correctly. Pay special attention to packages that use sensitive data and those relying on replaced environment variables to ensure they are executing as expected.
5. Secure Destination Environment: Ensure your destination SQL Server instance and SSISDB are configured with appropriate security measures, including strong passwords, least privilege principles, and network security.

Conclusion

Migrating SSIS Catalogs, especially those containing sensitive data and requiring intricate environment-specific adjustments, can be a complex undertaking. However, with the advent of tools like the SSIS Catalog Migration Wizard, this process has become significantly more manageable and secure. By eliminating the need to know the source SSISDB encryption key and automating the re-encryption process, coupled with the powerful ability to replace environment variable and parameter values during migration, the Wizard empowers administrators to perform SSIS migrations with confidence. This ensures the integrity and confidentiality of their sensitive data while proactively managing configuration changes throughout the transition. Embrace this powerful tool to streamline your next SSIS Catalog migration, and experience a truly hassle-free and secure transfer.

Installation

SSIS Catalog Migration Wizard can be installed as an extension to:

1. Visual Studio 2017, Visual Studio 2019 & Visual Studio 2022.
2. SSMS 18, 19, 20, 21(preview)
3. Standalone tool.

More details are available in this tutorial.

See more

The post Transferring Sensitive Data During SSIS Catalog Migrations to Another Server appeared first on AzureOps.

To resolve the CS2001 “Missing AssemblyAttributes.cs” error when executing an SSIS package on a deployed server, follow these steps to adjust folder permissions:

1. Open Windows Explorer and navigate to C:\Windows\Temp\.
2. Right-click the folder and select Properties.
3. Switch to the Security tab and click Advanced.
4. In the Permissions tab, select Change Permissions.
5. Locate the relevant permission entry, then choose Edit.
6. Ensure the following permissions are enabled with Allow checked:
   • Traverse folder / Execute file
   • Create files / Write data
   • Create folders / Append data
   • List folder / Read data
   • Take ownership
7. Click OK to save the changes and close the window.
8. Press Apply to confirm any prompts that appear.

Even if the logged-in user already has full control, modifying the permissions for the “Users” group resolved the issue.

See more

The post CS2001 Missing AssemblyAttributes.cs when executing SSIS package deployed to the server appeared first on AzureOps.

TITLE: Connection Manager
—————————— The specified provider is not supported. Please choose different provider in connection manager.
—————————— BUTTONS: OK ——————————

Cause of the Issue

The error typically occurs when the SQL Server Native Client required for database connectivity is missing or not installed properly. This provider is essential for SSIS to communicate with SQL Server using OLE DB.

Solution

To resolve this issue, you need to install the SQL Server Native Client on your machine. Follow the step-by-step guide below to download and install it properly.

Step-by-Step Guide to Install SQL Server Native Client

1. Download the Installer:

• Visit the Microsoft Download Center.
• Locate the SQL Server Native Client (sqlncli.msi) download link on the page.
• Click the Download button to start the process.

2. Install the Native Client:

• Double-click the downloaded sqlncli.msi file.
• Follow the on-screen instructions in the setup wizard.
• Accept the license agreement and complete the installation process.

3. Restart Visual Studio:

• Once the installation is complete, restart Visual Studio (which contains SQL Server Data Tools).
• Open your SSIS project again and check if the issue is resolved.

Conclusion

By installing the SQL Server Native Client, you enable Visual Studio (SSDT) to correctly recognize the required provider, resolving the error and allowing smooth SSIS operations. If the problem persists, ensure that your Visual Studio and SSDT versions are up to date.

Pro tips:
1. Learn how to migrate SSISDB from one server to another in just a few clicks.
2. You may come accross below error while trying to run older SSIS packages in SSIS 2022 (SSISDB).
The requested OLE DB provider SQLNCLI11.1 is not registered. If the 64-bit driver is not installed, run the package in 32-bit mode. Error code: 0x00000000. An OLE DB record is available. Source: “Microsoft OLE DB Service Components” Hresult: 0x80040154 Description: “Class not registered”.
Use the same above solution to fix this issue on the SSISDB server.

See more

The post The specified provider is not supported. Please choose different provider in connection manager SSIS appeared first on AzureOps.

An error occurred in the Microsoft .NET Framework while trying to load assembly id 65536. The server may be running out of resources, or the assembly may not be trusted. Run the query again, or check documentation to see how to solve the assembly trust issues. For more information about this error:
System.IO.FileLoadException: Could not load file or assembly ‘microsoft.sqlserver.integrationservices.server, Version=13.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91’ or one of its dependencies. An error relating to security occurred. (Exception from HRESULT: 0x8013150A)
System.IO.FileLoadException:…

Cause

When the backup of SSISDB from one SQL Server is restored on another SQL Server and creating an SSISB object on the target SQL Server Integration Services Catalog, you may get this error.

Solution

While the nature of the solution will depend significantly on the SQL Server versions, you can try the solutions below to resolve the issue.

Solution 1. Run the script below on target SSISDB.

USE [SSISDB]
EXEC sp_configure 'clr enabled', 1
RECONFIGURE
ALTER DATABASE SSISDB SET TRUSTWORTHY ON;
EXEC sp_changedbowner 'sa'

Solution 2. Recreate SSISDB in target SQL Server (Recommended).

Delete SSISDB (Integration Services Catalog) from the target SQL Server and create a new SSISDB in the target SQL Server. Once the SSISDB is created, migrate your SSISDB objects from source SSISDB to target. You can use the SSIS Catalog Migration Wizard to bulk-migrate SSIS objects with just a few clicks.

See more

The post An error occurred in the microsoft .net framework while trying to load assembly id 65536 SSIS appeared first on AzureOps.

The SSIS Integration Services Catalog consists of the following artifacts:

• SSIS Builds (.ispac files) – Contains several SSIS packages with project and package parameters.
• Environments – Stores configurations of SSIS projects. These variables are used to configure the SSIS project and package parameters of SSIS projects.

Pre-requisites:
1. User should have sufficient rights to create SSISDB Catalog under Integration Services Catalog in SQL Server.

Steps to create SSIS Catalog in SQL Server.

1. Connect to SQL Server using SQL Server Management Studio (SSMS). Right-click on Integration Services Catalog and select Create Catalog option.

2. On Catalog Creation Wizard, Enable CLR Integration. Provide a password for data encryption. Store this password for the future. And click OK.

This should create SSISDB catalog under Integration Services Catalog. You can now start deploying projects and executing SSIS packages.

Pro tips:
1. You can only create one SSISDB per SQL Server.
2. Steps to create SSISDB in Azure SSIS runtime are different; refer to this post to achieve this.
3. If you want to migrate an existing SSISDB from one SQL Server to another, you can use SSIS Catalog Migration Wizard for seamless migration in a few minutes.

See more

The post Create SSIS Catalog in SQL Server appeared first on AzureOps.

Prerequisites:
1. SQL: Server Data Tools for any visual studio version, e.g., 2017, 2019, or 2022. You can download it from this link.

Let’s first create a project in visual studio for the ispac file.

1. Launch Visual Studio and select “File” > “New” > “Project or Click Ctr + Shift + N.
2. Choose the ‘Integration Services Import Project Wizard’ project type, provide the Project name, Location, and Solution name, and Click Create.

There are two ways to open ispac file in Visual Studio

A. Open a project from a Project deployment (.ispac) file.

1. As shown in the image below, select the Project deployment file radio button, navigate to the folder where the .ispac file is located, and select it. Click Next.
2. Review your selection and click Next.

Visual Studio will automatically extract the SSIS package(s) from the .ispac file and load them into the Solution Explorer. You can then double-click on the package(s) to open them and make the necessary changes.

B. Open SSIS packages from SSISDB (Integration Services Catalog)

1. As shown in the image below, select the Integration Services Catalog radio button, and Enter the SQL Server instance name containing Integration Services Catalog (SSISDB).
2. Click the Browse button Next to the path and select the SSIS project you want to open. Click Next
3. Review your selection and click Next.

This will open the selected SSISDB project in Visual Studio.

Pro tips:
1. Using SSIS Catalog Migration Wizard, you can migrate SSIS Catalog items from one server to another in just a few clicks. It is an extension to Visual Studio, SQL Server Management Studio and can also work as a standalone tool.

See more

The post Open ispac File in Visual Studio appeared first on AzureOps.

The need for this activity might arise when:

1. When you want to migrate SSISDB from one server to another but in a different network (without direct connection).
2. When you want to migrate SSISDB from one server to another server that is under a different domain account.

All the above types of migrations can be achieved in just a few clicks using SSIS Catalog Migration Wizard by the below steps:

1. Export SSIS Catalog items from the source SQL Server (SSISDB) into the .scmw file.
2. Copy the .scmw export file to the target server.
3. Import the .scmw file to the target SQL Server (SSISDB).

What is SSIS Catalog Migration Wizard

SSIS Catalog Migration Wizard helps you migrate the full or part of the SSIS catalog to another SQL server. You can move the SSIS catalog to another server between any version of SQL Server (2012, 2014, 2016, 2017, 2019, 2022, 2025, Azure SSIS integration runtime, or Azure SQL managed instance). Apart from one-time migrations, this tool is designed to help you easily manage day-to-day SSIS catalog activities. Read more.

1. Export SSIS Catalog items from the source SQL Server into the .scmw file.

Launch SSIS Catalog Migration Wizard from your installed location and follow the below simple steps to export multiple SSIS projects from SSISDB in just a few clicks.

Choose Source SSISDB

Choose the SQL Server radio button and then provide the SQL Server instance name. To perform operations on the SSIS catalog, we have to use Windows Authentication, and the user running this should have the ssis_admin role.

Choose Target

Choose the SCMW file radio button and then the path of the local windows folder where we need to export the SSSI projects. Click Next.

Select the SSIS Catalog item to migrate.

From the source catalog view, select the desired SSIS projects that you need to export. Click Next.

Customize the target folder name and replace environment variable values steps are not applicable; hence click Next to skip these steps.

Review your choices and click Finish to export.

Review your choices made in all the above steps. If everything looks ok, click Finish.

2. Copy the .scmw export file to the target server.

Copy the .scmw export file to the target server or computer where you have access to the target SQL server (SSISDB). 

3. Import the .scmw file to the target SQL Server.

Launch SSIS Catalog Migration Wizard from your installed location and follow the below simple steps to import the .scmw file to the target SQL server (SSISDB).

Choose Source (scmw file)

Select the Source as scmw type and browse the export file using the file browser you have exported in step1. 

Choose target

Choose the target SQL server to import the scmw file and click Next.

Select the SSIS Catalog item to migrate.

From the source catalog view, select the desired SSIS projects that you need to export. Click Next.

Replace environment variable and parameter values.

Configure the key-value pairs you want to replace in the environment variable and parameter values. Suggest button will list suggestions for replacing values based on the selected Replace Scope. Click on the Ref column to view the affected environment variables and parameters, as shown in the image below.

Review your choices and click Finish to export.

We have seen how to export and import SSIS Catalog in just a few clicks using SSIS Catalog Migration Wizard.

Installation

SSIS Catalog Migration Wizard can be installed as an extension to:

1. Visual Studio 2017, Visual Studio 2019, Visual Studio 2022 &  Visual Studio 2026.
2. SSMS 18, 19, 20, 21.
3. Standalone tool.

More details are available in this tutorial.

Pro tips:
1. If you need to delete SSIS Catalog items in bulk, then select the items you want to delete from source SQL Server. Select target as scmw file and use Migration type as ‘move’. This will export selected catalog items into .scmw file and also delete them from source SQL Server SSISDB.
2. Learn how to copy SSIS environment from one SQL Server to another in just a few clicks.

The post Export and import SSISDB in just a few clicks appeared first on AzureOps.

What is SSIS Catalog Migration Wizard?

SSIS Catalog Migration Wizard helps in SSISDB migration to another SQL server. You can move the SSIS catalog to another server between any version of SQL Server (2012, 2014, 2016, 2017, 2019, 2022, 2025, Azure SSIS integration runtime, or Azure SQL managed instance). Apart from one-time migrations, this tool is designed to help you easily manage day-to-day SSIS catalog activitiesread more.

To start, launch the wizard from your preferred location.

Choose Source

Choose the SQL Server radio button and then provide the SQL Server instance name. To perform operations on the SSIS catalog, we have to use Windows Authentication, and the user running this should have the ssis_admin role.

Choose Target

Choose the SQLServer radio button as shown in the below image. Provide the target SQL Server host name.

Select SSISDB Catalog Items to Migrate

Choose the catalog items from the treeview that you wish to migrate.

Replace your environment variable values.

Configure the key-value pairs you want to replace in the environment variable and parameter values. Suggest button will list suggestions for replacing values based on the selected Replace Scope. Click on the Ref column to view the affected environment variables and parameters, as shown in the image below. Refer to the documentation for more details.

Complete the Wizard

In the end, you can view the summary based on your selections. Review the deployment summary. And if everything looks ok, click Finish.

Any warning or error during the migration gets shown next to the respective folder in the Result column tooltip of the grid. The success items are all noted as “Passed” in the above image.

Installation

SSIS Catalog Migration Wizard can be installed as an extension to:

1. Visual Studio 2017, Visual Studio 2019, Visual Studio 2022 & Visual Studio 2026.
2. SSMS 18, 19, 20, 21.
3. Standalone tool.

More details are available in this tutorial.

Pro tips:
1. This article describes how to Open SSIS Packages from ispac file.
2. Restoring SSISDB to another server can be problematic as the SSISDB database design differs in higher versions of SSISDB (Integration services catalog). If you want to create a new SSIS Catalog, follow this article.

The post Step-by-Step Guide : SSISDB Migration to a New Server appeared first on AzureOps.

What is SSIS Catalog Migration Wizard

SSIS Catalog Migration Wizard helps you migrate the full or part of the SSIS catalog to another SQL server. You can move the SSIS catalog to another server between any version of SQL Server (2012, 2014, 2016, 2017, 2019, 2022(preview), Azure SSIS integration runtime, or Azure SQL managed instance). Apart from one-time migrations, this tool is designed to help you manage day-to-day SSIS catalog activities with ease Read more.

How to Export SSIS Project from SSISDB in SQL Server

Launch SSIS Catalog Migration Wizard from your installed location and follow the below simple steps to export multiple SSIS projects from SSISDB in just a few clicks.

Choose Source SSISDB

Choose the SQL Server radio button and then provide the SQL Server instance name. To perform operations on the SSIS catalog, we have to use Windows Authentication, and the user running this should have the ssis_admin role.

Choose Target

Choose the SCMW file radio button and then the path of the local Windows folder where we need to export the SSSI projects. Click Next.

Select SSIS Catalog items to migrate

From the source catalog view, select the desired SSIS projects that you need to export. Click Next.

Customize the target folder name and replace environment variable values steps are not applicable; hence click Next to skip these steps.

Review your choices

Review your choices made in all the above steps. If everything looks ok, click Finish.

Monitor the progress

Monitor the progress. If there is no error or warning, you should be able to see the export file on the selected target folder.

Extract the .scmw export file to get the exported SSIS projects

Automation

If you want to automate the export SSIS project from SQL Server, use SSIS Catalog Migration Wizard command-line utility. You can run the below command from the command prompt or schedule it in any scheduler. Read more about it here.

"C:\program files (x86)\microsoft sql server management studio 18\common7\ide\extensions\ssis cataloger\SSIS.Cataloger.Pro.exe" /st:0 /ssn:LAPTOP-R9A0KU50 /tt:2 /scmwfp:"D:\SCMW exports\LAPTOP-R9A0KU50_2022-10-23_04-42-17.scmw"

We have seen how to Export SSIS project from SQL Server in bulk using SSIS Catalog Migration Wizard.

Installation

SSIS Catalog Migration Wizard can be installed as an extension to:

1. Visual Studio 2017, Visual Studio 2019 & Visual Studio 2022.
2. SSMS 18, SSMS 19.
3. Standalone tool.

More details are available in this tutorial.

Trusted by leading brands worldwide

The post Export SSIS project from SQL Server appeared first on AzureOps.

What is SSIS Catalog Migration Wizard

SSIS Catalog Migration Wizard helps you migrate the full or part of the SSIS catalog to another SQL server. You can move the SSIS catalog to another server between any version of SQL Server (2012, 2014, 2016, 2017, 2019, 2022, 2025, Azure SSIS integration runtime, or Azure SQL managed instance). Apart from one-time migrations, this tool is designed to help you manage day-to-day SSIS catalog activities with ease Read more.

Demo – Copy SSIS Environment variables to another server

Launch SSIS Catalog Migration Wizard from your installed location and follow the below simple steps to migrate SSIS environment variables from one SQL server to another.

Choose Source

Choose the SQL Server radio button and then provide the SQL Server instance name. To perform operations on the SSIS catalog, we have to use Windows Authentication, and the user running this should have the ssis_admin role.

Choose Target

Choose the SQL Server radio button and then provide the Target SQL Server instance name. Click Next.

Select SSIS environment(s) to migrate

From the source catalog view, select the desired SSIS environment that you need to migrate to the target SSIS catalog. You can also select multiple SSIS environments. Click Next.

Customize the target folder name.

If you wish to change the target folder name of the environment, you can edit the target folder name on this screen. This step is optional. Click Next.

Replace environment variable values

On this screen, you can replace environment variable values. As shown in the image below, you can replace the current value with the new one.

Review your choices

Review your choices made in all the above steps. If everything looks ok, click Finish.

Monitor the progress

Monitor the progress. If there is no error or warning, you should be able to see the SSIS environment in the target SSISDB.

Installation

SSIS Catalog Migration Wizard can be installed as an extension to:

1. Visual Studio 2017, Visual Studio 2019 & Visual Studio 2022.
2. SSMS 18, SSMS 19.
3. Standalone tool.

More details are available in this tutorial.

Pro tips:
1. Learn how to migrate SSISDB across different networks in just a few clicks.

The post Copy SSIS Environment variables to another server appeared first on AzureOps.