By Eric Vallo, EVT, and Thierry Audas, SAP

Canada Geese Flying at SunriseThe team at SAP Gold Partner EVtechnologies (EVT) has spoken, blogged, and webinar-ed more than a few times over the last six months about making a better path for your to get to SAP BusinessObjects Business Intelligence (BI), version 4.0. Whether you’ve been following the discussion all along or you’re just joining us now, we want to take some time to discuss formulating a strategy to migrate your existing SAP BusinessObjects BI environment to version 4.0. This is becoming even more relevant and timely as the release of version 4.1 of SAP BusinessObjects BI is planned for later this year and many users of versions XI, who haven’t moved to version 4.0, are now considering the jump to this upcoming release.

We’ve stared down small/flash cut systems. We’ve also stared down a few mammoth systems (not tens of thousands….hundreds of thousands of reports). In both cases, the considerations are strikingly similar.  Traditionally, letting your organization go into a migration blind  hasn’t been a big deal. EVT has done more than a few upgrades that involve simply picking up and moving everything over. An interesting trend in this latest flavor of SAP BusinessObjects BI is that of doing house cleaning before making the big move. But what does that mean? EVT recently spent a few weeks with a customer with one of those mammoth systems. We’re talking 850,000 reports. We’re talking about a migration path that took this customer from Business Objects 5.1 through to XI 3.1 and practically every version in the middle. There had never been an exercise to prune what was being carried forward.

Entrè Sherlock

While using EVT’s Sherlock product and the totally-free Sherlock Quick Sizer were the easy parts in putting together specifications for the design phase of this project, we really wanted to take this to the next level and give our customer a prescriptive path to content deprecation. What does that mean? You have junk you don’t even know about. It’s there. Trust our experience. That is where Sherlock came into play.

There are some really easy decisions to make to reduce the size and scope of your migration:

  • This was an easy one – the customer had 224,000 unread inbox documents.
  • There were 149,000 instances that had accumulated on reports with more than 30 instances. There were no regulatory requirements like SOX or HIPAA at play here. Just a lot of stuff.
  • There were a few other factors dictating an overall reduction, not to mention the 200,000+ reports that hadn’t been viewed in the last three years.

 

Let’s do the math for a moment: 224,000 + 149,000 + 200,000 (conservatively) = 573,000 reports. To keep score for just a second, that’s 573,000 reports that…

  • are consuming vast amounts of space (600 GB of storage, RAID, backed up).
  • don’t need to be migrated, saving potentially dozens of hours of regression testing, or even trial and error because you tried to migrate too many reports at one time.

 

Get Started Now

Evaluating the current state of your deployment isn’t rocket science, doesn’t take a great deal of time, and is a pretty simple recipe for success. What migration strategies have you employed to ease the move to SAP BusinessObjects BI 4.0? Pop over to the  version 4.0 upgrade page on the SAP Community Network (SCN) and to evtechnologies.com for live resources rich with info on making this move happen.