Skip to main content

Copying reports from one Report Server to another.

Microsoft released the Reporting Services Migration tool. A tool that migrates reports and other artifacts from one report server to another report server. It can also be used as a backup and restore tool for Reporting Services. The tool is available both as a command line tool, a GUI and a powershell script.

Current features and limitations
  • You can use RSMigrationTool or RSMigrationUI to backup your native report server.
  • To restore or migrate the native server, run the Migration.ps1 from a PowerShell console.
  • Source and target server must be SQL Server Reporting Services 2008 R2 or later.
  • Source server
    • Source server must be native mode using Windows authentication. (MS is working on support for SharePoint integrated mode and other authentication schemes.)
    • Permissions and roles from source server are not backed up o Configuration in source server is not backed up.
    • Reports and other artifacts in deeply nested subfolders may not be backed up. This is due to Windows OS restriction on the maximum length for the full path of the backup files and folders. (MS is working towards a solution.)
    • Linked reports are not support in SharePoint mode, hence not backed up.
    • Database connection to source server catalog is made using Windows Integrated credentials of the user running the tool.
  • Target server
    • Target server must be SharePoint integrated mode. (MS is working on support for native mode.)
    • The web application must be using Windows classic authentication mode. (MS is working on support for other authentication schemes.)
    • Target server must be correctly configured. Target document library and folder must be created. For SSRS 2012, service application must be created and configured.
    • The owner of Reporting artifacts after migration is set to the user who performed migration. (MS is working towards a solution.)
    • Subscription owners are set after they are migrated. If the owner does not have CreateAlerts/ManagedAlerts permission, the operation will fail.
    • Report parts are not linked correctly to the Report. (MS is working towards a solution.) o Database connection to target server catalog is made using Windows Integrated credentials of the user running the tool.

Although the tool lacks some important features, I’m happy to see there finally is a tool that simplifies this process.

Labels:

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more