Microsoft’s SQL Server 2008 is the most popular database… ever. Application vendors have relied on it to power their applications for many years. However, the SQL Server 2008 end of support (EOS) has been announced. It will take effect on July 9, 2019, raising the question of what to do with the thousands (hundreds of thousands) of currently running applications built around it. At EOS, security updates will stop, raising security and compliance issues and putting applications and the business at risk. Companies will also run the risk of customers migrating to another application.
Today, companies are looking for solutions that can archive inactive data from little used enterprise applications. Those applications can be decommissioned, saving the company the expense of keeping them running for little payback. But the question not addressed early enough in the project is what to do with all of the application’s legacy data – delete it or save it (and where). By migrating the legacy data to an intelligent archive, organizations can preserve the value of legacy application data, ensure regulatory compliance, and address any legal concerns.
Subscribe to the blog and get instant access to the crucial steps to ensure your cloud-based Office 365 migration goes smoothly.
I have written about application retirement a couple times in my blog. The concept is simple; organizations retire (shut down) aging business applications for several reasons all the time including cost reduction, application consolidation, risk reduction, and because of new regulatory and eDiscovery requirements. The big question continues to be what should be done with the associated application data? Before I address that question, let's look at a large, well known business application that many organizations are now looking at as a target for retirement - Documentum.
Most organizations eventually retire (shut down) aging business applications for several reasons including cost reduction, application consolidation, risk reduction, and because of new regulatory and eDiscovery requirements. However, one question that is not usually addressed early on is; what should be done with the associated application data?