That is what I would recommend too. We almost did that but the opposite way before we went live with 8.0. Our DBAs recommended we move to Oracle. We had a RAC instance built and a new RHEL app server but there just wasn't enough time to keep the project moving and change infrastructure. Darn, guess we'll have to stay on SQL Server (although I was looking forward to having Linux apps servers).
Jason On Mon, Jul 29, 2013 at 1:12 PM, Longwing, Lj <[email protected]> wrote: > ** > Claire, > If I was in charge of that move, I would install everything using exact > same versions and everything on a new app box, pointing to a new SQL Server > DB, then I would use RRRChive to move all records in all forms from the > Oracle Remedy server to the SQL Remedy Server, and then of course analyze > any custom workflow that uses direct sql, or anything that does sql > directly to ensure that it all works properly....I wouldn't expect it to be > a HUGE project...largest single problem I would expect to have would be > reporting related, if you have connections directly into the DB. > > > On Mon, Jul 29, 2013 at 2:06 PM, Sanford, Claire < > [email protected]> wrote: > >> ** >> How hard would it be to move from an Oracle DB to a SQL DB? >> >> There are so many issues that would be solved if we moved off oracle. >> BUT, if it is a huge undertaking, it may not be worth the trouble. >> >> >> >> ITSM 7.6.04 SP2 >> ARS 7.6.04 SP3 >> Oracle 11.2.0.3.0 - 64bit Production >> Win 2008 Server >> >> Claire Sanford >> Information Systems Division >> Memorial Hermann Healthcare System >> [email protected] >> >> >> >> _ARSlist: "Where the Answers Are" and have been for 20 years_ > > > _ARSlist: "Where the Answers Are" and have been for 20 years_ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
