Category Archives: Application Retirement
The Future of Applications (2): Lowering Costs and Complexity
This is my second blog in a series on the subject of “Informatica & Applications”. You can read my previous blog here:
It’s strange how IT has become so complex. When we started out so many years ago computing was the answer to everything. It was going to make us more productive and was going to allow us to spend so much more time with our loved ones. Do you remember that time when people said “we’ll have a paperless office, and we’ll be finished by 5pm.”?
I wish!
Don’t Forget The Legacy Applications After Data Center Consolidation
As part of their cost cutting program, organizations are consolidating data centers and the applications within them. Federal and state agencies in the public sector are among those where IT consolidation and moving applications to the cloud are top priorities as part of an overall goal to increase efficiencies and eliminate costs. In other industries, many consolidations are also under way due to mergers and acquisitions and other cost cutting initiatives. As you plan or undergo a consolidation project, you also need to plan for the retirement of legacy, redundant applications that are left behind.
Eliminating Up To 95% Of Legacy Costs As Part Of Your Journey To The Cloud, With Application Decommissioning And Archiving
We’re all familiar with those legacy applications that no longer add value, but still absorb significant costs. These redundant applications may be left due to mergers and acquisitions, IT consolidation, business modernization, application migration, or moving to a cloud-based or software as a service environment. If you are an EMC customer, many of you may be undertaking projects to consolidate your IT stack to increase efficiency, and moving gradually towards a private or hybrid cloud environment. As you are virtualizing, re-platforming, and migrating your hardware and software, what do you do with the old applications that are left behind? (more…)
The Secret To Retiring Applications – Flawless Data Validation
Applications are retired (sunset or decommissioned) when they become dormant or read-only. This occurs as a result of mergers and acquisitions or through modernization efforts and is a natural part of Application Information Lifecycle Management. While the applications may be no longer needed, the data they contain cannot be discarded. As a result, many organizations have hundreds, even thousands, of defunct applications that are consuming budget dollars, taking up data center space, complicating IT management, and generally just getting in the way. The challenge is getting rid of applications without getting rid of the data which is tightly coupled to them. (more…)
ROI Tool To Help Make The Business Case For Database Archiving, Application Retirement, Test Data Management, And Data Masking
Though the benefits of containing the size of your databases by archiving seems obvious in terms of saving costs and improving performance, quantifying those benefits in terms of dollar savings requires more thought. The same is true when it comes to the costs that can be eliminated by retiring redundant legacy applications. Some of the savings may come from hard dollar costs such as:
- Storage
- Backup devices
- Maintenance contracts
- Software licenses (more…)
Achieving IT Efficiency Through Consolidation And Legacy Application Retirement In Banking And Capital Markets
One of the top challenges among financial firms of all sizes is how to efficiently manage information within their organization in the face of explosive data growth. More and more data needs to be retained for a longer period to meet regulatory compliance. At the same time, they need to meet customer SLAs. The wave of mergers and acquisitions in the financial services industry leads to IT consolidations effort that leaves many legacy applications behind. The cost savings from IT consolidations would only be realized by retiring those legacy applications to eliminate the associated operational and maintenance costs. These legacy applications are kept around because the data needs to be retained for compliance.
Realizing The Cost Savings From Healthcare Reforms With Legacy Application Retirement
The American Recovery and Reinvestment Act of 2009 (ARRA) provided the healthcare industry incentives for the adoption and modernization of point-of-care computing solutions including electronic medical and health records (EMRs/EHRs). This modernization effort is leaving legacy applications behind, which are no longer of high value, but is costing the organization a lot of money. These legacy applications are kept around because the data needs to be retained for compliance and accessibility to the data needs to be maintained. This is a very expensive proposition for most organizations. (more…)
Realizing The Cost Savings of Mergers & Acquisitions by Retiring Legacy Applications
Following a Merger and Acquisition (M&A), there is usually a focus on consolidating the two companies’ IT systems, leaving behind many redundant legacy applications. Until those legacy applications are shut down, you haven’t realized the cost savings of the consolidation. However, those old applications may contain data that’s no longer used for daily operations, but need to be retained for regulatory compliance. Keeping those applications up and running, just to retain the data within them introduces operational, business and legal risks. It is likely that the IT staff who have the expertise about those applications are no longer with the company, and without them it may be difficult to impossible to access the data in a meaningful way, in the time required, for an audit or eDiscovery request.
Series: Architecting A Database Archiving Solution Part 4: Archive Repository Options
During this series of “Architecting a Database Archiving Solution”, we discussed the Anatomy of A Database Archiving Solution and End User Access Requirements. In this post we will review the archive repository options at a very high level. Each option has its pros and cons and needs to be evaluated in more detail to determine which will be the best fit for your situation.
(more…)
Series: Architecting A Database Archiving Solution Part 3: End User Access & Performance Expectations
In my previous blog as part of the series, architecting a database archiving solution, we discussed the major architecture components. In this session, we will focus on how end user access requirements and expected performance service levels drive the core of an architecture discussion.
End user access requirements can be determined by answering the following questions. When data is archived from a source database:
- How long does the archived data need to be retained? The longer the retention period, the more the solution architecture needs to account for potentially significant data volumes and technology upgrades or obsolescence. This will determine cost factors of keeping data online in a database or an archive file, versus nearline or offline on other media such as tape. (more…)
Loading ...