Database evaluation
Because it’s the foundation of your system
The database of a software could be compared to the foundation of a house.
You don’t see it, you rarely think about it, but you sure don’t want to have to change it once it’s built.
There are four factors to ponder to analyze the quality of a database when choosing an ERP of any software:
- what’s the database management system?
- is the database secured?
- is the database accessible?
- is the well built?
4 factors to consider in a database evaluation
#1 On what DBMS runs the software?
What is the database management system that your system runs on? Is it a popular system? Or is it a proprietary database?
Aim for a software that runs on one of the major database systems like Oracle, Microsoft SQL Server or even open-source database systems like MySQL or PostgreSQL.
If the system is still using an old database system – let’s say like dBase – you may run into troubles. In that case, make sure the vendor has a clear plan on how and when they will update the DBMS. Changing the database system on an implemented software is major work that can lead to problems.
#3 Is the database secured
Some software have a very good security system on the front-side – what the user can or cannot do through the user interface – but almost no security on the database-side. That could mean unauthorized access to the data for someone either inside or outside the company (and that person won’t even have to be that knowledgeable to achieve it). That means security risks you don’t want to take. Make sure that won’t happen.
A system that is secured on both side – user interface and database – is a sign of a good product.
#3 Is the database accessible?
Another important part of database evaluation is to make sure you have access to the data. You want to be able to connect directly with the database through programs other than the software developed by the vendor, especially if it’s an ERP. Whether it’s for connecting two software together or to later allow business intelligence, a database has to be accessible.
Remember, the software is the property of the vendor, but the data is yours! So make sure you have access to the database at all time. You probably won’t be able to write in the database, but you have to be able to extract data (and not just through the software reports).
#4 Is the database well-built?
A well-built database gives a good indication of the quality a software. While technically it’s not your problem if it’s not – you’ll rarely directly interact with the database – looking at the database structure may give an indication of the quality of the software and if the supplier is knowledgeable and pays attention to details.
Are they using the database best practices? Is it well normalized? Are the objects named well? A good DBA will be able to evaluate those things in an hour.
Also, a well-built database will ensure long-term performance and will make sure that bridging is an option (connecting your different software together).
This analysis is of a lesser importance if you chose one of the major systems on the market since they have a full team of knowledgeable database developers. But for smaller software, it may be worthwhile. While you can’t look at the code behind the software to see if it’s well-written, you do have access to the database.
Final words
Doing a good database evaluation will ensure that you won’t run into problems later with your software. The bigger the system, the more thorough the evaluation should be.
Home > ERP Implementation Project > ERP Selection > Database Evaluation
