Cookie preferences

Choose which optional cookies we may use. Your choice applies to this browser for 12 months, and you can change it at any time.

Needed for the site to work and to remember your cookie choice. These are always on.

Cookies used (1)
  • motio_consent · Motio · 12 months
    Remembers your cookie choices and the consent ID used to record them.

Google Analytics tells us which pages people visit and how they use them, so we can improve the site.

Cookies used (2)
  • _ga · Google Analytics · 2 years
    Distinguishes visitors.
  • _ga_<id> · Google Analytics · 2 years
    Keeps session state.

LinkedIn, Google Ads and Salesloft measure which campaigns bring people here, show our ads to people who have visited before, and identify which companies visit.

Cookies used (5)
  • _gcl_au, _gcl_aw · Google Ads · 90 days
    Measures ad clicks and conversions.
  • li_fat_id · LinkedIn · 30 days
    Conversion tracking, retargeting and analytics.
  • li_giant · LinkedIn · 7 days
    Conversion tracking for groups of members.
  • bcookie, lidc, li_sugr, UserMatchHistory, AnalyticsSyncHistory · LinkedIn (linkedin.com) · 1 day – 1 year
    Identify the browser and match visits to LinkedIn members for ads.
  • sliguid, slireg · Salesloft Scout (salesloft.com) · 7 days – 1 year
    Identifies visiting companies for sales follow-up.
Skip to content
Case study · Cognos

Motio paid for itself in one content-store crash.

How a Fortune 500 healthcare provider recovered a corrupted Cognos content store, and months of work, with version control.

Fortune 500 healthcare provider and a leading U.S. provider of dialysis services
Mark Mortensen
Mark Mortensen
BI Systems Administrator, DaVita
~$500K
saved in content-store recovery costs
Months
of development work recovered
9,000
Cognos users supported
The challenge

DaVita deployed BI content across Dev, Test/QA, and Production with a process that felt safe but offered no real rollback and no versioning of content-store objects, putting months of development at risk every day. Then the unthinkable happened: after a routine reboot, Cognos wouldn't restart. A rare bug had left the content store with circular references (CMSYS5230), and the team was stuck.

The solution

DaVita had implemented Motio just four months earlier. Its version-control capabilities were used to pinpoint the cause of the failure and restore the corrupted content-store database. Motio's support team walked DaVita through recovering the affected reports and packages, and going forward, Motio automated environment-to-environment deployment, including security configuration and data sources.

“When our Dev content store crashed, we had just implemented MotioCI four months prior. If we had not had MotioCI, we would have been in a really, really bad situation. Right there, it paid for itself.”

Mark Mortensen · BI Systems Administrator, DaVita
The results
✓Restored a corrupted Cognos content store that was otherwise unrecoverable from within Cognos
✓Saved approximately $500K versus the cost of manual repair and recovery
✓Avoided losing months of development work that lived only in Dev
✓Simpler, automated deployments between environments, security settings and data sources included

“Motio has made it so simple to deploy between environments.”

Mark Mortensen · BI Systems Administrator, DaVita

See what Motio can do for your Cognos team.