How to Handle Support for Decommissioned Enterprise Apps

It’s only a matter of when your organization faces this dilemma.
members-only post 3-min read
SHARE
How to Handle Support for Decommissioned Enterprise Apps
Photo by Hans Eiskonen / Unsplash

Microsoft recently nixed support for SQL Server 2005. You might not care about the announcement if your organization runs dB2, Oracle, MySQL, or another backend database. Also, if it had upgraded from the 2005 version over the past decade, the news probably didn’t matter much to you.

Still, odds are that many organizations continue to run legacy versions of the database. Case in point: Even though Microsoft has been touting Windows 10 for a while now, many companies never migrated their employees from Windows XP. This is astonishing, since XP launched on October 25, 2001. As an interesting aside, nearly all automated teller machines (ATMs) continue to run XP.

Work in enterprise IT long enough, as I have, and it’s only a matter of when—not if—your organization faces a similar dilemma. At some point, a software vendor is going to stop providing support for key enterprise applications and technologies. In this post, I’ll discuss the main options for organizations to consider.

Options

The six main options for organizations facing this dilemma include:

If you want to view this post, you'll need to suscribe to this site.

Sign up to continue reading this content.


Before You Go...
If you'd like to support my writing efforts, I'd appreciate it.

𝗧𝗜𝗣 𝗧𝗛𝗘 𝗔𝗨𝗧𝗛𝗢𝗥