Carolina Biological reduces data by 1.5 Terabytes

Carolina

Success Story – A Strategic Role for IT

At Carolina Biological Supply, IT plays a central role in promoting the company’s core values of innovation, quality and service. In particular, IT is critical to fulfilling the “Carolina Pledge” which guarantees 100% customer satisfaction. The IT team plays an important role in ensuring that Carolina’s customer service and loyalty metrics remain consistently strong.

Oracle® JD Edwards at Carolina

Carolina purchased and installed Oracle JD Edwards OneWorld XE in 2003. The company upgraded to version 8.11 in late 2006. In late 2010, after four successful years on 8.11, Carolina upgraded to 9.0. Carolina uses Oracle JD Edwards to manage finance, inventory, manufacturing, logistics and customer service. The company keeps up-to-date on tools releases and runs EnterpriseOne on an IBM iSeries as well as a Windows application server.

Consistent Performance Through Proactive Data Management

The IT team wanted a tool that delivered results quickly and also allowed easy access to archived data. After assessing various solutions, including using native Oracle JD Edwards purging tools, the IT team chose ARCTOOLS. Key to the final decision was the fact that ARCTOOLS was a native iSeries tool that had already been used successfully at hundreds of Oracle JD Edwards customer sites worldwide.

 

Purging and archiving your data not only makes life easier for the IT team, it also makes business sense. The ARCTOOLS project really delivered a quick win. ARCTOOLS is a powerful and easy to use tool that delivers results quickly and gives a strong return on investment.


Tony Price

Director of Technology Carolina Biological Supply

Results

  • Reduced Oracle JD Edwards production data by 500 gigabytes
  • Overall space savings of 1.5 terabytes
  • Saved at least 12 hours in data conversion during 9.0 upgrade
  • Improved ERP performance
  • More efficient database maintenance and backups

 

A Quick Win

The project was completed in just eight weeks. It was quick, did not demand a large investment of time from the internal team and did not disrupt end users.

Download the full case study here »

Connect with us
Loading