Roger, We're doing the same thing now and we successfully tested the following scenario (from 7.0.1 to 7.5 P6):
Build the new server(s) with version you want to go to (SQL 2008 and ARS 7.5). Back-up your existing server. Perform an upgrade-in-place of SQL Server 2003 to 2008 and apply updates, patches, etc. Perform an upgrade-in-place of ARS. You now have a system on your old server that matches the new server (same database and ARS version). Back up the database on the old server. Restore it to the new server. Tweak SQL Server permissions changed during the restore (verify Remedy account is dbo). Fire up all of the services. Craig Carter Information Technology Manager, RSP -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Nall, Roger Sent: Wednesday, December 08, 2010 9:30 AM To: [email protected] Subject: Upgrade suggestion ** ARS 7.1 patch4 SQL2k WIN2003 We are going to be upgrading to ARS 7.5 patch 7 and SQL 2008 at the same time. All hardware will be new. I am looking for suggestions on how to handle the change in ARS and SQL at the same time. Any help would be appreciated. Thanks, Roger Nall Manager, SA Business Intelligence/Remedy Desk Phone: 972-464-3712 Mobile: 973-652-6723 Helpful Links: | Reports <http://bi.eng.t-mobile.com:8080/InfoViewApp> |SA_Suggestion Box <http://saintake.t-mobile.com/> | SA_Trouble Ticket <http://natweb.eng.t-mobile.com/sites/TTWeb/CreateTicket.aspx> | _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
