Moving checklist 20194/20/2024 Tuesday, Febru5:15:54 PM - Mustafa ELmasry delete old key but when start report server service again restore in table "The feature: "Scale-out deployment" is not supported in this edition of Reporting Services. Wednesday, Febru5:27:13 AM - Vivek Siddhapura Vivek, are you sure you deleted the old SSRS instance name? Thanks for the prompt response, this problem solved which comes because i was not update encryption key.Īfter came other error 'System.Guid' to type 'System.String'. Thursday, Febru6:20:17 AM - Vivek Siddhapura I exactly followed the steps and it worked. Thursday, 1:14:49 AM - MOHAN BABU SUKUMAR Does the service automatically upgrade the DB when the service starts? What am I missing? Where's the upgrade step? You can't tell me a 2012 SSRS database is compatible with 2017. TomV, I've used this process going from 2008R2 to 2012 to 20 without any problem. Just compared a set of 2017 database to the restored copy of those same databases on a new 2019 SSRS instance after following your procedure and there are 30 new and 23 updated objects and 1 that doesn't exist in the ReportServer database on the 2019 instance. So it appears the upgrade process for the ReportServer and ReportServerTemp databases is performed by the SSRS Service upon startup. My question is should I move 2008R2 to an intermediate version, like 2012, before going to 2019? What do you suggest? And Subscriptions not working and not even editable. For example, reports are missing data sources. I used this process to upgrade 2008R2 to 2019. I want to refer back to your comment on May 17, 2022. I'd say 2012 as an interim step would be a good idea. I've never gone all the way from 2008R2 to 2019 but the most recent one I've done going from 2017 to 2019 started off originally on 2008R2 but had stops at 20. The user accounts and Keys table issues would have stumped me without this article anticipating the problem and solution! Thanks again. Thanks for this guide - I've tried rs.exe for a migration and upgrade from SSRS 2012 to 2019 and had nothing but permissions and other errors. Thanks for this! This worked perfectly for migrating a reporting services database from SQL 2016 to SQL 2022! I haven't had the need to move one to 2022 yet. Thanks for this! It worked successfully for migrating a reporting services database from SQL 2012 to SQL 2022! :) I carried out all the steps and it works fine but I have a problem, the groups and users that I had in the security section are not migrated, nor are the access permissions in the reports based on the roles. Migrate a Reporting Services Installation (Native Mode)īeatriz, sounds like you may have a problem with the encryption key. SQL Server Reporting Services Migration Tips WHERE InstanceName = 'SourceSsrsServerName'įollowing are some links to more info on migrating SQL Server Reporting Services Run DBCC CHECKDB on ReportServer and ReportServerTempDB.Update Compatibility Level if going to newer version SQL Server.Restore ReportServer and ReportServerTempDB from backups.Stop Reporting Services thru Reporting Services Configuration Manager.Backup ReportServer and ReportServerTempDB together.ChecklistĪlso, here's a handy checklist to use if you like simple checklists like You'll probably want to disable jobs while testing. WITH DEFAULT_SCHEMA=ĪLTER ROLE ADD MEMBER Ĭheck for errors in the error log and there should not be any more login failures. Go back to the ReportĬREATE USER įOR LOGIN MOVE N'ReportServerTempDB_log' TO N'C:\Program Files\Microsoft SQL Server\MSSQL14.SQL2017\MSSQL\DATA\ReportServerTempDB_log.ldf',Īt this point we need to be sure the logins and users are in sync, but we'llĭigress briefly to show what happens if you omit this step. MOVE N'ReportServerTempDB' TO N'C:\Program Files\Microsoft SQL Server\MSSQL14.SQL2017\MSSQL\DATA\ReportServerTempDB.mdf', MOVE N'ReportServer_log' TO N'C:\Program Files\Microsoft SQL Server\MSSQL14.SQL2017\MSSQL\DATA\ReportServer_log.ldf',ĪLTER DATABASE SET COMPATIBILITY_LEVEL = 140ĪLTER AUTHORIZATION ON DATABASE:: TO ĭbcc CHECKDB() WITH NO_INFOMSGSįROM DISK = N'C:\backups\ReportServerTempDB_migration.bak' - edit backup directory and file name MOVE N'ReportServer' TO N'C:\Program Files\Microsoft SQL Server\MSSQL14.SQL2017\MSSQL\DATA\ReportServer.mdf', FROM DISK = N'C:\backups\ReportServer_migration.bak' - edit backup directory and file name
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |