BACKGROUND IMAGE: leszekglasner/Fotolia
Fine-tuning the decision to opt for third-party DBMS tools
Today's top database management vendors, including Oracle, Microsoft, IBM and MongoDB, boast plenty of native tools for database tuning and administration. But third-party database tools have gained enterprise traction over the years and offer IT teams an appealing -- and often cheaper -- alternative.
It helps that major third-party database tool vendors like Quest Software, Idera, CA, BMC Software and Redgate are continuously trying to step up their game by offering unique or enhanced capabilities not always found in the top database management system tool sets.
But, along with the many benefits of these offerings, there are a fair share of potential drawbacks and obstacles to consider when deciding whether to deploy third-party database tools. That decision can become more complex when factoring in on-premises versus cloud database systems. According to Gartner, 75% of all databases by 2022 will be deployed or migrated to a cloud platform, making cloud deployment a core consideration for most companies.
This handbook offers advice on evaluating and using third-party options in both on-premises and cloud database systems. First, we discuss the importance of ensuring that third-party database tools meet defined business goals and take into account orchestration, data governance and integration. Next, we detail the top reasons to deploy third-party offerings, which include filling a functionality gap, complimenting existing services and creating heterogeneous database administration. And finally, we list common mistakes database professionals need to avoid when migrating databases to the cloud as well as verifying that third-party tool sets work with database-as-a-service systems.