Quantcast
Channel: SQL Server Integration Services forum
Viewing all articles
Browse latest Browse all 24688

Is there a recommended way to migrate a 2012 SSISDB to a 2017 SQL server?

$
0
0

Hello,

I have an SSISDB catalog ( with a couple hundred packages), on a SQL Server 2012 that I want to migrate a newly built 2017 SQL Server (with SSIS, and a fresh and still empty SSISDB catalog).

Of course, I do not wish to redeploy the 200 packages t the new server.

Is there a sure way (steps ?) of doing this migration ?

So far the few migration trial I attempted (using Backup & Restore of both the SSISDB database and its Master Key) failed:

While SSISDB database is on CL 140, the Catalog Properties show a Schema Build of 11.0.7462.6 (of the source server)

The "Database Upgrade" wizard (invoked from Integration Services Catalogs by right clicking SSISDB) fail with the following error:

Microsoft SQL Server Management Studio -- The system cannot find the file specified (System), etc...

Executing

use SSISDB

exec catalog.check_schema_version @use32bitruntime = 0 --- or 1

shows the following error:

Msg 27222, Level 16, State 1, Line 7

The required components for the 64-bit edition of Integration Services cannot be found. Run SQL Setup to install the required components

Msg 6522, Level 16, State 1, Procedure internal.check_schema_version_internal, Line 0 [Batch Start Line 6]

A .NET Framework error occurred during execution of user-defined routine or aggregate "check_schema_version_internal"

[……]

and trying to run any of the packages failed with the above error

I ran SQL Setup  to repair the SQL install. that did not fix the problem

I un-installed SSMS then installed a new version (18.1), but that too did not fix the problem.

Any help resolving this issue is greatly appreciated.

Thanks


Viewing all articles
Browse latest Browse all 24688

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>