Traditional reporting systems like SSRS have served enterprises well for years. However, with the rise of interactive dashboards and real-time insights, companies now require more dynamic and visually rich reporting solutions. This is where Power BI Report Server steps in.
This article provides a complete guide to help you understand the migration process, benefits, and a real-world use case where 2000+ reports were successfully migrated.

Real-World Use Case: 2000+ Reports Migration

Large-scale migrations are often viewed as high-risk, time-consuming projects. However, leveraging the right automation tools changes the math entirely.

The Benchmark: In a recent enterprise deployment, we successfully migrated over 2,000 reports in approximately 40 minutes using SSRS Reports Migration Wizard.

Why Organizations are Making the Switch

• Unified UX: Consolidate Power BI reports (.pbix) and paginated reports (.rdl) into a single portal.
• Enhanced Performance: Improved processing engines and scalability.
• Legacy Debt Reduction: Modernizing connection strings and centralizing data sources.
• Interactive Analytics: Moving beyond static tables to drill-through dashboards.

This use case clearly demonstrates that with the right strategy, even large-scale migrations can be executed efficiently.

Strategic Migration Workflow

To efficiently migrate SSRS reports to Power BI Report Server, follow this streamlined process:

Step 1: Select the Source

• Choose the SSRS/Poweer BI Report server or import a .SRMW file
• Ensure the source environment is accessible

Step 2: Select the Target

• Provide connection details for the Power BI Report Server
• Choose destination (same server/different server/folder)
• Validate connectivity

Step 3: Choose Report Items to Migrate

• Select reports, folders, datasets, and data sources
• Use filters for bulk selection

Step 4: Manage Folder Mapping

This step is available when “Rename target folders during migration” is enabled. It is useful for organizing and restructuring reports in the target environment.

• Rename folders during migration
  Example: Finance → Finance_New
• Migrate to a different folder name
  Example: Reports → Prod_Reports
• Consolidate multiple folders into one
  Sales Asia, Sales EU, Sales NA → Sales

Step 5: Update Data Source Connection Strings

• Fetch all data sources used in selected reports
• Review and edit connection strings
• Update credentials manually
• Optionally convert embedded sources to shared sources
• Changes apply only after migration completes

Step 6: Review Changes

• Verify summary of new, updated, and skipped items
• Export summary if needed
• Confirm configurations before execution

Step 7: Finish and Validate

• Execute migration
• Review logs and migration summary
• Validate data accuracy and report performance
• Rerun process if needed

Installation

SSRS Reports 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, 22
3. Standalone tool.

Standalone Usage

Don’t use Visual Studio? You can still run the wizard as a standalone tool:

Launch SSRS.Reports.Migration.Wizard.exe.

Download the .vsix from here.

Rename the .vsix to .zip and extract it.

FAQ

Conclusion

To successfully migrate SSRS reports to Power BI Report Server, organizations must adopt a structured, scalable, and automation-driven approach. As demonstrated in the real-world case of migrating 2000+ reports, it is possible to achieve seamless transformation with minimal disruption and post migration efforts.

By upgrading to Power BI Report Server, businesses gain access to modern analytics, interactive dashboards, and a unified reporting platform that drives better decision-making.

Read full customer testimonial on the Visual Studio Marketplace.

Watch a quick demo

The post Migrate SSRS Reports to Power BI Report Server appeared first on AzureOps.

Traditionally, administrators had to download each report manually from the Report Manager portal, or write complex scripts using SSRS SOAP APIs. Both approaches are time-consuming and prone to errors. Fortunately, there is now an easier way to achieve this: using the SSRS Reports Migration Wizard.

What Is the SSRS Reports Migration Wizard?

The SSRS Reports Migration Wizard is a tool from AzureOps designed to help you migrate SSRS content (native mode) between servers or to/from an SRMW export file.
It supports migrating:

• Folders
• Reports
• Shared datasets
• Shared data sources
• Subscriptions
• Roles

The wizard gives you a guided interface to select exactly which objects to migrate, and optionally adjust connection strings along the way.

When to Use Export + Import via SRMW File

Using an export file gives you flexibility:

• You can create a backup snapshot of your reports/datasets/data sources
• You can move content offline — export on one server, then import later on a different server
• It helps in server upgrades, consolidation, or reorganizing your SSRS environments

If you prefer a direct server-to-server migration, that’s also supported by the wizard. But export/import via file is safer and useful, especially when network access or permissions between servers is constrained.

Step-by-Step: Exporting SSRS Items to SRMW File

Here is a step-by-step walkthrough of how to carry out the export. You can follow along with the video, or use these instructions with screenshots in your own environment.

1. Launch the Migration Wizard

• From SQL Server Management Studio (SSMS), open the SSRS Reports Migration Wizard.
• (If installed as an extension, you’ll find it under the Tools menu.)

2. Start the Export Process

• Click Next to begin.
• Enter the source SSRS web service URL (e.g. http://yourservername/reportserver) along with domain credentials.
• Click Connect to load the contents of that SSRS instance.

3. Select the Export File Target

• On the next screen, choose the SRMW file option as your export target.
• Browse to the folder where you want the export file to be saved.
• Specify a file name (for example, MySSRSExport.srmw).
• Click Next to continue.

4. Choose SSRS Items to Export

• You’ll see a tree view of all SSRS objects: folders, reports, datasets, data sources.
• Check the boxes next to the items you want to export.
• After your selection, click Next.

5. (Optional) Update Data Source Connection Strings

• On the next screen, you can update the connection strings and credentials for data sources.
• These settings will be baked into the SRMW file and used when you later import the content.
• If you don’t need to change anything, you can skip this.
• When ready, click Next (or Finish, depending on wizard layout).

6. Review & Confirm

• The wizard will show a summary of what will be exported.
• Confirm your selections and click Finish (or Export) to start the process.

7. Complete Export & Verify

• The wizard runs, exporting all chosen items into your SRMW file.
• When it completes, open File Explorer and navigate to the export folder you chose.
• You’ll see the .srmw file.
• (Optionally) You can unzip or inspect its contents to verify that your reports, datasets, and sources are included in the proper folder structure.

What’s Inside the SRMW File & How It Helps

The SRMW file is essentially a packaged archive that contains:

• Report definition files (RDLs)
• Dataset definitions
• Data source metadata (connection strings, credentials)
• The folder hierarchy (to preserve navigation/organization)
• Standard subscriptions definition, etc.

When you later run the wizard’s Import mode, the tool reads this file and recreates the selected SSRS items into the target server.

Using this intermediate file gives you:

• A portable, versionable package
• A safety buffer (you can inspect or edit before import)
• The ability to stage/migrate content in controlled stages

Pro tips:
1. Test first with a limited set of reports to ensure everything works as expected.
2. Double-check your data sources — mismatches or missing credentials are common issues.
3. Use clear naming conventions for your export file (with timestamp) so you know which export is which.
4. Keep a backup of your export file in a safe location.
5. Make sure the target SSRS server is compatible in terms of version and features.
6. Check permissions: the account you use must have sufficient rights on the source SSRS items.
7. Learn how to migrate SSRS report server items from one report server to another.

The post Download all SSRS Reports from Report Server appeared first on AzureOps.

In this case study, we examine how Leidos, USA , completed an AWS SSRS migration involving more than 80+ SSRS reports, despite having no connectivity between the source SSRS server and the AWS environment.

Background: AWS SSRS Migration with Network Isolation

Leidos was modernizing its infrastructure by moving workloads from an on-premises data center to AWS. Their legacy SSRS server (Windows Server 2016) was scheduled for decommissioning.

Over the years, the server had accumulated:

• 80+ SSRS reports
• Deep folder hierarchies
• Shared data sources

Due to security policies, the on-prem SSRS environment and AWS were completely disconnected, making a traditional SSRS migration approach impossible.

This made the project a textbook example of a disconnected SSRS migration.

Key Challenges in Disconnected SSRS Migration

• No direct network access between on-prem SSRS and AWS
• Inability to use live source-to-target SSRS migration
• Risk of missing reports, folders, or shared data sources
• Manual redeployment not feasible for large SSRS estates
• Need for a safe backup before decommissioning

Solution: File-Based SSRS Migration to AWS

To address these challenges, Leidos used SSRS Reports Migration Wizard in Standalone Mode, leveraging its offline / file-based SSRS migration capability.

This approach is ideal for:

• AWS SSRS migration
• Air-gapped or disconnected SSRS environments
• Secure enterprise networks

AWS SSRS Migration Process (Step-by-Step)

Step 1: Export SSRS Reports from On-Prem Server

On the source SSRS server, the tool:

• Automatically discovered reports, folders, and shared data sources, subscriptions, roles etc.
• Displayed the full SSRS hierarchy for validation
• Exported all selected items into a single migration file

During export:

• Individual .rdl files were generated for each SSRS report
• Folder structure and metadata were preserved

This created a complete offline SSRS backup, a key requirement in regulated environments.

Step 2: Transfer Migration File to AWS (Disconnected Network)

Since the environments were disconnected:

• The migration file was securely transferred using approved methods
• No firewall changes or temporary network access were required

This step highlights the core benefit of disconnected SSRS migration to AWS.

Step 3: Import SSRS Reports into AWS Environment

On the AWS-hosted SSRS server:

• The migration file was imported
• Folder hierarchy and shared resources were recreated
• Data source connections were updated for AWS databases

After import, all SSRS reports were available for validation.

AWS SSRS Migration Results

• 80+ SSRS reports successfully migrated to AWS
• No network connectivity required between environments
• Folder hierarchy and report dependencies preserved
• Minimal downtime
• No manual report recreation

The migration was completed smoothly despite being a fully disconnected SSRS migration.

Additional Benefit: SSRS Backup and Disaster Recovery

An unexpected advantage of the file-based approach was backup:

“The tool creates .rdl files for each report… making it an easy way to back up SSRS reports, data sources, and folders.”

This makes the solution useful not only for AWS SSRS migration, but also for:

• SSRS backup
• Disaster recovery
• Compliance and audit scenarios

Why This Approach Works for AWS SSRS Migration

• Designed for disconnected and air-gapped networks
• Supports offline SSRS migration to AWS
• Preserves full SSRS hierarchy
• Generates reusable .rdl files
• Suitable for enterprise security requirements

Read full customer testimonial on the Visual Studio Marketplace.

Watch a quick demo

The post SSRS Migration Case Study: Migrating SSRS Reports in a Disconnected Environment appeared first on AzureOps.

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.

What Is SSRS Reports Migration Wizard?

SSRS Reports Migration Wizard is a tool that enables you to:

• Migrate reports, shared datasets, shared data sources, linked reports etc.
• Copy subscriptions (standard and data-driven)
• Review and update connection strings and credentials
• Migrate between servers, folders, or environments
• Export and import SSRS items using a lightweight .SRMW file format
• Perform offline review and validation before actual migration

The wizard is available as a Visual Studio extension and as a standalone tool.

Prerequisites:
Before Migrating SQL Server Reports
1. You have access to both source and target SSRS servers.
2. Your user account has:
-at least Browser role on the source–
-at least Publisher role on the target
If you’re unsure how to grant access, follow the instructions in the Granting Access Guide.

Use Cases

• Migrating from dev to test/prod environments
• Consolidating multiple SSRS servers
• Backing up and archiving SSRS artifacts
• Migrating from the old SSRS report server to the new server.
• Migrate SSRS reports to Power BI report server.
• Moving SSRS content before end-of-support deadlines.
• Automating report deployments using the command-line utility.
• Compare source and target servers and export a diff CSV before committing changes.

Step-by-Step SSRS Report Migration Process

Follow the below steps to achieve SSRS report migration from one server to another.

Step 1: Select the Source

Choose your source SSRS server or a .SRMW file created from a previous export.

Step 2: Select the Target

Provide connection details for the destination SSRS server. You can migrate to a different server, or a different folder on the same server.

Step 3: Choose Report Items to Migrate

Select specific folders, reports, datasets, and data sources using a tree view. Filters and checkboxes make large-scale selection easy.

Before finalising the migration, use the Compare with Target feature to export a CSV diff of what exists on the source vs. the target server. This gives you a full audit trail — useful for compliance reviews, change management approvals, or simply verifying nothing was missed. The export includes item-level status: new, changed, unchanged, or missing.

Step 4: Manage Folder Mapping

This step is available only when Rename target folders during migration is enabled. Use this screen to define how source folders should be created in the target environment.

Step 5: Update Data Source Connection Strings – Migrating SSRS Data Sources

SSRS Reports Migration Wizard includes an optional step to update data source connection strings during the migration process. This is particularly useful when migrating reports and datasets from a source server to a target server that uses different connection details.

Fetch Data Sources

On this screen, click the Fetch Data Sources button. The wizard will scan the selected SSRS items (from the previous screen) and populate a grid with all connections that can be updated.

Each row represents a unique connection used by your reports or shared data sources.

View and Manage Connections

The grid displays the Extension, Connection String, and Credential Retrieval method for each data source. Click the Edit link in the Manage column, which allows you to modify the connection.

Convert to shared data sources if connection exists – If this option is selected, the wizard will attempt to convert embedded data sources in reports to shared data sources during deployment, provided a shared data source with the same connection details is available in the selected SSRS items for deployment.

Update Properties

When you click Edit, a new dialog box appears (labeled “Manage Connection Properties”). Here you can:

• Review the Shared Data Source(s) using this connection and Report(s) using this connection as an embedded data source.
• Modify the Connection String.
• Specify Credentials (e.g., Windows credentials or a user name and password) under “Log into the data source”.
• Click Save to apply the changes.

Important Notes

• The wizard cannot retrieve passwords from embedded or shared data sources on the source report server. The wizard will guide you to convert them ot shared data sources and provide credentials.
• The Dependent Objects shown in the grid are those that have a connection embedded within them. These objects are directly using this connection.
• The changes you make are not committed to the target server until the wizard completes the migration.
• If no connections are found for the selected items, a message box will inform you that there are no connections available for update.

Step 6: Review Changes

The wizard shows a migration summary with new, changed, or skipped items. You can export this list or proceed with the migration.

Step 7: Finish and Validate

Once migration is complete, a final summary screen shows migrated item counts and logs. You can rerun this process anytime.

Installation

SSRS Reports 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, 22
3. Standalone tool.
4.Command-Line Usage.

Standalone Usage

Don’t use Visual Studio? You can still run the wizard as a standalone tool:

1. Download the .vsix from here.
2. Rename the .vsix to .zip and extract it.
3. Launch SSRS.Reports.Migration.Wizard.exe.

Pro tips:
1. Use export-then-import (.SRMW file) rather than direct server-to-server when network access between environments is restricted — especially useful for cloud or air-gapped targets.
2. Run Compare with Target first to get a full diff before committing any changes.
3. Migrate permissions separately using the role migration step — verify subscription accounts exist on the target before migrating subscriptions to avoid silent failures.
4. Use the CLI for repeatable deployments — once you’ve validated your migration manually, script it for future environment rebuilds.
5. Learn how to export all SSRS objects from the report server. Learn how to migrate SSRS Reports to Power BI Report Server.

The post How to Migrate SSRS Reports from One Server to Another (Step-by-Step) 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.