This forum is deprecated.
When it comes to choosing the right database to support your application it can feel like a daunting task. To make life easier, here are a few topics to consider helping you pick the right database for you and your customers.
ISV’s choose InterBase because of its super low total cost of ownership, speed of development, ease to support and commercial grade database features. Below is an overview of InterBase vs a select few databases.
Summary: InterBase is faster, vastly more scalable, is packed with superior disaster recovery and data protection compliance features that are key to maintaining both you and your customer’s reputations. Additionally, Change Views adds a zero cost and highly scalable replication engine API that reduces significantly both data movement and replication licensing costs for the lowest total cost of ownership.
InterBase vs MySQL
Summary: Open-source is not always free. Oracle’s MySQL is a popular open-source database that is free to download, but you’ll need to buy an annual subscription for each deployment. InterBase gives you better value. When it comes to protecting your data and ensuring business continuity, it’s critical that you carefully consider both data backup and data encryption. InterBase supports both online data backups and Transparent Data Encryption (TDE) in all paid editions, while these features are only available for the most expensive MySQL Enterprise edition.
MySQL architecture centers on server-to-server replication, and doesn’t offer a mobile database. InterBase Change Views is built to easily handle data movement between a large variety of remote devices - either locally or distributed - making it ideal for modern scalable replication requirements.
InterBase v MSSQL
Summary: MSSQL is a powerful top end database that comes with top end pricing, if you want the business critical features like Transparent Data Encryption (TDE). TDE helps businesses conform with Data Protection laws and best practice and work towards standards like PCI / HIPPA compliance. TDE is in all paid editions of InterBase, a feature that is only available in MSSQL Enterprise.
On disaster recovery server costs; InterBase includes the license for a secondary hot disaster recovery server, for MSSQL you have to pay for an additional server license. To put it another way, an 8 CPU server with TDE and hot disaster recovery is over $107k cheaper with InterBase!
Without the mobile presence, the MSSQL replication technologies focus on server to server rather than enablement of a large number of distributed remote devices that InterBase Change Views also enables.
InterBase v SAP SQL Anywhere
Summary: Originally Sybase SQL Anywhere, it was acquired by SAP in 2012. Being a SAP company its agenda is heavily focused on SAP product development and feature requirements. There is also clear indication from SAP that HANA is their platform for the future leaving many wondering what will happen to SQL Anywhere.
Both InterBase and SQL Anywhere provide strong mobile offerings and data change tracking capabilities. While Change Views is built into the InterBase core, MobiLink is a charged extra per device.
InterBase vs SQLite
Summary: InterBase IBLite and SQLite are both free database offerings. SQLite lacks certain features to achieve SQL92 compliance, specifically the lack of Stored Procedures.
For business data on mobile, InterBase ToGo is packed with superior disaster recovery and data protection compliance features that are key to maintaining both you and your customer’s reputations. With protection throughout the development life cycle InterBase massively reduces the risk of fines and regulatory action in the event of lost data.
SQLite is basically a flat file on steroids; SQLite does offer the same level of database support to ensure data integrity and doesn’t for high concurrency. Because of this, it is not really suited for ISV development.
Interested in Using InterBase?
ISV / OEMs and VARs can get special pricing by setting up a VAR agreement. Read more about becoming an InterBase VAR or contact your sales rep for more information.
Reduce development time and get to market faster with RAD Studio, Delphi, or C++Builder. Design. Code. Compile. Deploy.
Start Free Trial
Free Delphi Community Edition
Free C++Builder Community Edition
I use SQLIte a lot with node.js and asp.net (when i have to) and you are quite right, there are some shortcomings in that department that should have been highlighted.
PostgreSQL is cool, but i must admit I havent tested it beyond the superficial
why not also consider PostgreSQL towards you
IMHO the biggest shortcomings of SQLite are omitted. - No proper datetime datatype. - If a field is null in the first record of a returned dataset the driver is unable to determine the datatype of the field. This is a consequence of fields being of variable datatype, regardless of the CREATE TABLE statement. For example when using SQLite with FireDac bytes fields cannot be read unless a work around is implemented to ensure that the field in the first record is not null.