Database management

How to Choose the Right Database Management System ?, IT News, ET CIO

By Dhrumil Dhakan

Data-driven businesses largely depend on a database management system that can provide high availability and also allow the business to expand its capabilities. While database management system use cases may vary from organization to organization, it is important to keep in mind that the end result is essentially the same, a reliable database that can minimize downtime.

During a panel discussion on Data Thinness: Making the Right Decision, industry leaders question how to choose the right database management solution for a data-driven organization.

DBMS can help an organization deal with issues like lost revenue, as every minute of downtime can lead to thousands of dollars in losses, and apart from that it can also affect the reputation of the business. and its business outlook.

Legacy systems are not suitable for today’s business workloads and high availability requirements. It can also be a challenge due to the high cost of licenses, license complexity, increased maintenance and operating costs, and audit risks. This has led companies to migrate to alternatives, but how do you make the right decision?

“I think the approach modern organizations need to take more and more is to determine the use case and then determine the database that will serve that use case well rather than betting on a data for all business needs, ”said Soumendu Ganguly, CPO & Head Tech Strategy, CAMS on whether to choose legacy systems or the new database today.

Many agree that the one-size-fits-all approach is no longer relevant and it is important to keep this in mind when choosing what is right for the organization. “We’re basically arguing for a matrix process and a Thinktree process, basically you have to go ahead and decide why? Why would you want to change, if you are migrating from an existing application? Determine the why and why can be anything, it can be financial, it can be the database you are currently using and what future projects you have and what features you want to offer through the app that might be suitable to workload or operability, ”says Deepanshu Sharma, Director – Support Services, EDB to determine the reason for this change, to make it easier to choose the database your organization needs.

Sharma further explains that once the why is understood, it is important to consult with your administrators and developers as they are the main stakeholders when choosing the right database. “We’ll decide if the underlying technology or database you choose is easy to maintain? Is it scalable? Make sure that safety compliance can be maintained on this. And the developers will also be essential because you must have this knowledge base within your team to be able to use the functionalities that you bring with the new database ”,

Obviously, there are a lot of things to consider when moving from a legacy system to a more contemporary database, which include both business and technical considerations. Elaborating on this issue, CK Prasad, Executive Director of RailTel Corporation of India Ltd, states the following.

“Some of them include, first of all, certainly the cost of it, in the sense that the initial cost, the cost of migration and also the cost of the life cycle which are the post-migration operations, the maintenance and again we have to see that update patches, security update and stuff like that until we remove the database ”,

Although these have been from a technical standpoint, many companies change for business reasons. “For example, when you create structured, semi-structured, or unstructured data that you want to keep, you might need to migrate from one database to maybe two different databases, maybe databases. non-relational data and relational databases. So we also have to see, this business requirement maybe, to improve the performance of your entire application, ”continues Prasad.

He also stressed that it is important to see if the company will hire new skills for the new databases or if they will retrain the same team or if the company will migrate to the cloud etc.

CK mentioned the different qualities to look for, including reliability, fault tolerance, architecture, clustering, data criticality and, most certainly, support. If the business can get support beyond its IT teams, OEMs, consultants, systems integrators, etc.

“Definitely reliability, fault tolerance, architecture, grouping of those based on the criticality of the data, that comes into play, and certainly support, so you can get support beyond that.” from your IT team from the OEM and even from consultants or system integrators… ”,

“It’s not the database, but the expertise you have to use it that will define the performance of this database. this database. This is a key element that organizations consider, ”says Soumendu.