Retiring old 2012 SQL Server, need to migrate SSIDB and Jobs from SQl Server Agent into an existing SQL Server 2012 Server

  • I am looking to retire a SQL Server to cut down on licensing costs and need to move the SSIDB database and several jobs onto an existing 2012 SQL server. What is the best way to do this? Is it as simple as backing up the Database and importing it into the new environment? Then what about about the store jobs?

    Thanks.

  • pow12390 - Wednesday, July 19, 2017 12:39 PM

    I am looking to retire a SQL Server to cut down on licensing costs and need to move the SSIDB database and several jobs onto an existing 2012 SQL server. What is the best way to do this? Is it as simple as backing up the Database and importing it into the new environment? Then what about about the store jobs?

    Thanks.

    You can't import from a database backup but you can restore the database which would replace the existing database.
    You can script out the jobs on the to be retired server and move those to the new server. You can select the Jobs folder in SSMS and then go to the menu to view and select Object Explorer details. All the jobs will show up in the details window. You can select all or some of them and right click, select script jobs as create. 
    You would want to look at your existing maintenance on the current server and figure out how to incorporate the maintenance on the soon to be retired server. You wouldn't want duplicate jobs. Some jobs shouldn't be scripted out and moved depending on what they do. And the schedules could need to change if the addition of the new jobs results in some conflicts with run times so you would want to take that into consideration.
    You can move packages from SSISDB to another servers SSISDB. You can often import from the old server to the new or if create ispac files by exporting the packages from the soon to be retired server. And just like with the jobs, you would want to think about what the packages are doing and if they need anything else set up on the server - such as does it need access to other executables, are they using proxies, etc. This article has a pretty good walk through, screen shots on moving the packages: 
    Copying a Package Between Servers

    Sue

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply