i have all scom roles and databases running on a single server, including audit collection. after three blissfully ignorant years of running an apparently unsupported configuration without incident, upgrading from RTM to SP1 to R2, and upgrading in-place from sql 2005 to sql 2008, the new performance reports in the new OS MP have brought it to my attention that SQL was initially installed with the wrong collation method. all my databses are the correct SQL_Latin1_General_CP1_CI_AS, but the *server* level collation is Latin1_General_CI_AI. and these new reports will not run, throwing: An error has occurred during report processing. Query exectution failed for dataset 'PerformanceData.' Cannot resolve the collation conflict between "Latin1_General_CI_AI" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation. my DBAs tell me the server-level collation cannot be changed without rebuilding the master database, which is not a good idea, and i'd be better off backing up the databases, reinstalling sql, and restoring the databases. the thing that makes me most nervous about this is the SCOM reporting/SSRS, because doesn't it customize the stock SSRS somehow? so let me know if this sounds right: (stop scom services) 1. backup OM, OMDW, OMAC databases (make note of reader/action/etc. accounts used) 2. uninstall scom reporting 3. uninstall/reinstall sql +reporting services 4. restore databases (use same accounts/permissions as before) 5. reset SQL reporting services with resetSRS.exe(?) 6. reinstall scom reporting (custom install without datawarehouse piece since i already have a datawarehouse.) do i need to do #5 if i am completely uninstalling sql in #3? i basically borrowed from http://technet.microsoft.com/en-us/library/cc540369.aspx thanks in advance.

Hi John, if you completely remove SSRS you don't need #5. Instead of backup/restore, if you're rebuilding on the same server you can just detach and then reattach the databases. If you plan to upgrade you SQL version to R2 you can check this guide: http://nocentdocent.wordpress.com/2011/02/14/how-to-migrate-opsmgr-to-sql-server-2008-r2/ - Daniele, Microsoft MVP OpsMgr Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. This posting is provided "AS IS" with no warranties, and confers no rights. http://nocentdocent.wordpress.com http://www.progel.it

no need for number 5. clean install is already reset. looks likw you are doing clean rebuild of reporting services. you will need to configure ssrs and check ifbit working by going to the website http://localhost/reports and see if you get a good view with icons and all (no reports there yet). after this is confirmed you install scom reporting without the database option as you mentioned. and remember the scom CU updates. If its working you will see your reports appearing in the scom console within minutes to hours. This does mean that if you created custom reports without storing them in a management pack and your scheduled report settings will be gone (clean install, right?).so first check your current console if you have schedules or custom reports which did not come with a management pack. If they are from an mp they will auto-load again within an hour or so.Bob Cornelissen - BICTT (My BICTT Blog) - Microsoft Community Contributor 2011 Recipient

Hi John, if you completely remove SSRS you don't need #5. Instead of backup/restore, if you're rebuilding on the same server you can just detach and then reattach the databases. If you plan to upgrade you SQL version to R2 you can check this guide: http://nocentdocent.wordpress.com/2011/02/14/how-to-migrate-opsmgr-to-sql-server-2008-r2/ - Daniele, Microsoft MVP OpsMgr Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. This posting is provided "AS IS" with no warranties, and confers no rights. http://nocentdocent.wordpress.com http://www.progel.it

no need for number 5. clean install is already reset. looks likw you are doing clean rebuild of reporting services. you will need to configure ssrs and check ifbit working by going to the website http://localhost/reports and see if you get a good view with icons and all (no reports there yet). after this is confirmed you install scom reporting without the database option as you mentioned. and remember the scom CU updates. If its working you will see your reports appearing in the scom console within minutes to hours. This does mean that if you created custom reports without storing them in a management pack and your scheduled report settings will be gone (clean install, right?).so first check your current console if you have schedules or custom reports which did not come with a management pack. If they are from an mp they will auto-load again within an hour or so.Bob Cornelissen - BICTT (My BICTT Blog) - Microsoft Community Contributor 2011 Recipient

Hi, I think you can also refer to Kevin’s post: Moving the Data Warehouse Database and Reporting server to new hardware–my experience http://blogs.technet.com/b/kevinholman/archive/2010/08/25/moving-the-data-warehouse-database-and-reporting-server-to-new-hardware-my-experience.aspx Hope this helps. Thanks.Nicholas Li - MSFT Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi, I think you can also refer to Kevin’s post: Moving the Data Warehouse Database and Reporting server to new hardware–my experience http://blogs.technet.com/b/kevinholman/archive/2010/08/25/moving-the-data-warehouse-database-and-reporting-server-to-new-hardware-my-experience.aspx Hope this helps. Thanks.Nicholas Li - MSFT Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.