BT chooses Optim to manage data


BT chooses Optim to manage data

Warwick Ashford

BT has implemented Optim software from data management company Princeton Softech to cope with spiralling data volumes generated by thousands of daily support calls.

After a market search for the most appropriate data archiving software, BT chose Optim because of its ability to segregate historical and current data.

By reducing the amount of information in the production database, less disk space is needed forapplication data, cutting storage costs, said BT. With less information to analyse, applications run faster and operations run more efficiently.

Amdocs Clarify, which works with an Oracle database, is used to handle about two million fault reports a year. BT said it was facing a significant problem managing the data, particularly with the rapid rate of growth in new repair and order cases.

The purging tool BT was using was capable or removing only up to 600 cases daily, but new Clarify cases were being added at a daily rate of 5,000.

BT said once Optim was installed, the organisation was able to put a long-term data retention strategy in place and begin purging out-dated cases from its database.

Cases are now retained on the online database for up to two years before the data is compressed automatically and moved to a separate archive file.

BT said Optim's automated data management strategy had eliminated data archiving backlogs.

According to Princeton Softech, the implementation of Optim at BT represents one of the first ever deployments of this approach to enterprise data management.

Email Alerts

Register now to receive IT-related news, guides and more, delivered to your inbox.
By submitting your personal information, you agree to receive emails regarding relevant products and special offers from TechTarget and its partners. You also agree that your personal information may be transferred and processed in the United States, and that you have read and agree to the Terms of Use and the Privacy Policy.

COMMENTS powered by Disqus  //  Commenting policy