Few topics are as controversial in the Oracle community as ULAs. Oracle ULA devotees say they help companies save money and maintain an ongoing relationship with Oracle; those who have had negative experiences (or are simply very cynical) say that ULAs are a trap with their benefits greatly exaggerated.
As it often does, the truth lies somewhere between the two extremes; done right, a ULA can be a smart investment. Companies can use the tools they acquire under the ULA to propel projects, spur departmental growth, and help maintain a strong relationship between their organization and Oracle. Indeed, when ULAs are good, they’re very, very good. But plenty of IT vets that have wrestled with Oracle can also tell you that when ULAs are bad, they are horrid – and Oracle won’t pull punches with your organization just because you have a ULA.
So – should your organization acquire a ULA? It’s a tough question with no easy answer. Most of the time, it just comes down to whether or not a ULA fits the organization’s current set of needs.
But figuring out whether your organization is a good candidate for an Oracle ULA is rarely straightforward. Your Oracle rep will always sing the praises of ULAs and swear they can only improve your shop; many IT consultants have their own agendas and prejudices, and not everyone is a grizzled IT director that knows Oracle agreements, contracts, and products like the back of their hand.
This is why I teamed up with LicenseFortress to produce a book specifically about ULAs – the good, the bad, and the ugly. Released February 2, 2021, The Completely Unauthorized Oracle ULA Guidebook – Everything Oracle Doesn’t Want You to Know spells out nitty gritty details to consider before taking the plunge.
Is This Book for You?
Even if the ULA option isn’t front and center for your organization right now, reading this book will put you in a good position to advocate for your department and its needs when the topic rears its head (and, if your organization uses Oracle products, it will eventually).
Anyone who touches any part of an Oracle agreement should give this book a read. This includes legal (especially since in-house legal teams rarely have much Oracle expertise) and anyone in procurement that might assist with the deal. In the IT department the usual suspects – IT directors, CTOs, systems analysts, DBAs, network engineers, MIS directors, and IT coordinators – should all become acquainted with this volume. Even if you aren’t personally responsible for negotiating or selecting a ULA, it’s good to be aware of the information the IT director should know when making this decision, especially if there’s a possibility you’ll be called into strategy sessions or asked to offer an opinion.
Knowledge is Power
But, in addition to what we’ve outlined above, there’s more! Here’s a list of important details you’ll learn by reading this book:
-
The three ideal scenarios for organizations signing onto a ULA (if these don’t describe you, please reconsider)
-
The four kinds of IT shops that should never use a ULA
-
When ULAs attack: How one organization saved $3.9 million
-
How to negotiate with Oracle and why you should never accept Oracle’s first proposed ULA (just plan to kick back the first offer)
-
Making life easier for future you: Preparing to exit the ULA before you sign the ULA
-
How to get the most from your Oracle ULA
-
The truth about Perpetual Unlimited Licensing Agreements (PULAs)
-
Certifying out the smart way: The steps you need to take to get out of your ULA unscathed
Also, the book contains tech humor (at least I find it funny) and great artwork by Michael Cucurullo. It’s a good read and will help organizations of all kinds and sizes understand their options when it comes to Oracle agreements, both ULA and otherwise. And remember – you’ve already put a large quantity of money into your Oracle ULA – why not further protect your investment by taking the time to read this, too?
