Risks of Not Migrating

[MUSIC PLAYING] Risks of not migrating-- it's probably the inverse of benefits of migrating. But what are the risks of not migrating? Where do we start? You're operating an oil platform. You've got security problems. You're much more liable for security breaches. You're operating on an unsupported platform. If it breaks, you're stuck. I mean, those are a lot of the risks we see all the time. I mean, yeah, I can't say enough about that. Those are the risks of not migrating. Yeah. Yeah. Yeah. Right? It's also getting left behind. I think the ability to adopt new technology like we just mentioned quickly, AI, if you're not poised to take advantage of that, even if you don't know exactly how you're going to use it now, your competitors probably are poised to take advantage of it. So getting yourself in a position so that you can move quickly on platforms that are maybe a little bit more flexible around new technology adoption is probably a good thing. Yeah, and you just reminded me of something there about risk. It's quantifiable. People-- when it comes to risk, it's quantifiable, and they make a judgment call because I remember a few years ago, people were still using 11g on Oracle. And you're like, that's completely out of support. Still? Yeah, but they're still using it, right? Oh, yeah. I could probably go through our list of users and come up with a significant number that are on old platforms. Oh, yeah. Yeah. Yeah. So it's like it's quantified, and so they're willing to take the risk. It's the unknowns that's the problem. Well, yes. Right. You have to be bold. I mean, eventually if you don't update, the platform, the vendors, the OS will abandon you. That's the thing about technology. You can't stay still forever. So some of our tools are very, very flexible about supporting older versions. They've always worked on those versions. We don't ever end support for those versions. And I know that sometimes I hear from our customers, I'm so glad because I'm using Oracle 9. And so you hear these things, and you're like, OK. Yeah, well, I'm happy that we're there for you, but I can't imagine a lot of vendors are. So technology is a moving-- you could try to get ahead of the curve and get benefits ahead if you want, but you can't stay still forever. Eventually, you'll be obsoleted out of your support, of your skill set for people who know that technology and are really good at it. The OS will stop supporting it. So you can't stay still forever. It's just about what is your appetite for the unknown, as you said and how cutting edge, bleeding edge, modern-edged do you want to be. And in today's world, too, with all of the security threats, if you're on an old version of a database which requires an old version of an operating system, now there's 15 different known exploits to that operating system version that you can't patch. Now you're opening yourselves up. You're a toy store for a hacker. Yeah, and we've talked about those instances. I forget what the name of the company was. Mike, we talked about it where the breach in that company started because somebody didn't update a piece of software-- Target was one of them. --on their desktop. Yeah, and then someone exploited that breach. Now that software had already been patched, but the customer didn't pick it up. Didn't pick up those updates, right? Yeah. And that was a way in. So security technology, the costs I imagine over as technology debt gets larger, the cost to support operating systems, et cetera. And other-- And your opportunity costs too. What I was trying to get at is opportunity cost, right? If you're not updating, means you're not taking on new features, new functionality, whether that's within the database platform or just within the ecosystem that you're now participating in. And so all of your technology is suffering because of that. So how much faster could you be doing it, how much better could you be doing things, how much more other technologies could you bring in if you were set to do it. But if every-- sorry. If every adoption of a new technology means you have to take on a huge migration project because you've left all this data out there, then your appetite gets even less and less to do it. It becomes something that's a lot more painful than it needs to be. All right. And I think the last one that it's a natural extension is that lack of migration and that willingness to sit there because it's the path. It appears to be the path of least resistance. You now become Dr. No to your business and forever telling them they can't have what they need to be a data-driven company because we've got this piece of technology that we feel comfortable with. And we don't want to take that risk. And so now it's the risk reward and doing that analysis up front to figure out that you know what? It's just not an option anymore. So yeah, from a technical perspective, from a security, all of those things, but at the end of the day, these databases are there to drive the business. And you're going to get to a point where you just can't do what they want. And if that's the answer that you continually give, you're probably going to be looking for another job. Yeah, excellent point. It's risk versus reward. If you're that risk averse, eventually you're going to get yourself to a point where you're not serving the business. And you're right. Yeah. I had somebody tell me once, there's no such thing as not broken in technology. That's right. So you can't use it-- not broken, don't fix it kind of thing. Right, because it's all somewhat