Backup and replication options.
At the first based on my experience we need to calculate software or customer requirements and after that choose the best option. Today all databases have the same options with little difference like Data types, HA, Performance, Security, Backup/Recovery, etc.
for example if you want to design a software with just 5 to 20 users, is that reasonable to use Oracle database service ?
however, from a programmer's point of view evaluating Relational Databases are rated by features like Datatypes, Functions, Index types and etc, DBA's (Database Administrators) vision is different. So my list is
- TCO (Total cost of ownership)
- High Availability Solutions.
- Backup / Restore solutions.
- Data Capacity and Security.
- Memory Management.
- Inmemory Database, Tablespace, Table.
- 3rd Party software
1. Backup and recovery
2. Data security
An Oracle logo.
Top in my list
A single reason is not enough, we can rank the following reasons:
- Operational Performance (OLTP, DWH - ETL)
- Relate to hardware such as disk (storage), memory, cpu and how well they can use them
- Data Capacity
- Data Security
- Application Support
- Vendor Support
The most important is "Solid backup and recovery solution." Imho.
Performance, Security, Quiet Easy to Implement the database Solution, Excellent database tools for managing the Database Environment for example Microsoft SQL Server Management Studio.
Performance, Security, Vendor Support and Price
Definitely Performance, Data mining, easy use.
We should evaluate mainly performance of the database as well as pricing of the database.
- If you want to host application which has small amount of data and does not have secure content in it you can go for open source databases.
- vice versa, if your data has secure or critical contents in it then we should consider security features of database as well.
- one more important feature we need to consider now a days is parallel distribution/parallel computing feature e.g. Postgresql / greenplum has this feature.
Modeling features (from physical to business), sql optimization / mdx support, easy of use
mainly the performance. For RDBMS you would not be having any performance issue. But when it comes for data loading, RDBMS would not be a good take. This of an MPP where the data is spread accross segments
Scalability and performance, both in relation to volume of data and concurrent queries.
scalability and platforms DBMS runs on
Ease of use
Examples of complex statements or auto creation of queries
If it covers all of the project needs/specifications.
Vendor support, product track record, scalability, clustering options and security.
First Knowledge of the platform, performance, backup/restore...
Easy integration, fast ,scalability to needs and support for all developer APIs
only one reason as of today, that is transactional atmoicity, don't see any other; you open source them with light versions and see the miracles; graph databases are evolving and once there cn be a better fit not just for social as they are today;
Performance, ease of use, scalability and support for all developer APIs.
There's no "most important" criteria when choosing a tool, and a RDBMS is just a tool. If you're running Twitter, then the key factor is performance. If you're running a small medical clinic software, then you need data integrity above the others.
The most important criteria for our customers at NuoDB is that our distributed SQL database has a flexible deployment model that allows them to run the database on a single server machine, across machines in a data center or public cloud, and even on a global basis (across multiple data centers) without having to architect a new solution for each use case.
Scalability, performance and Business Intelligence capability from ETL to warehousing and analytics. Also how well the database solution can be leveraged in an enterprise development organization. There are many more options these days but not from a mature development to deployment and maintenance standpoint.
Reliability, scalability, security, performance, ease of management.
The RDBMS that are known for its Scalability, Availability and its OLTP performance. However am exploring its Analytical functional capabilities. I have been using Sybase IQ EDW. its serves the purpose now. However moving towards building an Enterprise Data Warehouse –Data Lake, researching about MSSQL DW 2014
performance, scalability & security
Can't answer this blindly. Depends on why I'm researching a relational db technology and what the requirements are.
Ability to retrieve as and when required in any format to give valuable insights to business.
Easy for support and use. Set of high availability features.
operational efficiency and simplicity of use and understanding ( set of features ) has a high value in any case.
performance, security, and it allows OO_RDBMS
Wide adoption, Performance, Scalability, Replication, Failover.
1. Performance 2. Ease of using analytic functions 3. Industry hold
Performance and security
Existing organisational capabilities. e.g; introducing Oracle to a team already skilled in MSSQL would likely be a mistake. Beyond that, I haven't 'researched' RDBMSs for some time. The choice is usually clear for me. MSSQL, MySQL or Postgres.
Scalability and performance.
Do we actually need any of the 'relational' part or can we leverage an object db or something even more lightweight?
Organised, Relationship establishment between objects, Atomic, Security.
Performance, period. Needs to provide a variety of ways to move and process data quickly leveraging disk, processors, RAM, and IO.
Meets Availability requirement, performance and recovery time objective.
Ease of use is also important as well as utilities to load and unload data.
Compatibility. If the database engine doesn't work well with the software you want to use it with, the rest of the features just don't matter. After that, performance and scalability.
Ease of use, scalability, and portability.
Performance and more performance. Go hand in hand with the best technologies Disk.
The data bases footprint in the current market. For example I am reviewing things. MS Access has been a relational database I thought had a footprint and a future. The stuff I read online about the 2013 upgrade and Office 365 have me thinking maybe my ideas need to shift to something else.
Scalability, reliability, performance, ease of management and adherence to standards.
Replication, failover and performance.
Reaction to system failure
The most important criterion is whether the DB comes with a mature BI stack.
The metadata and the less "case when" script.
Concurrency control, analytic functions and indexing options
Ease of use as for uniformed command line and syntax, JOIN performance and features to be able to create sub join / sub view. Community support and widespread use. Availability on documents and technical know - how.