Here we are in early 2017 fulfilling the promises we made back inNovember 2016 to deliver a new version of our award-winning InterBase RDBMS. We referred to InterBase 2017 as Project BigBang during development because of the positive impact InterBase is delivering. We have been listening to you, our customers. This result is created by delivering some of the most sought after features, ISV’s and Fortune 100 customers have been asking for such as SQL Derived Table Support, and Server wide performance monitoring to enhance the ability of existing applications to use InterBase as a back-end RDBMS, and that’s just the beginning.
I want to say a big thank you to those who have been personally involved in the beta program, your input is invaluable and is shaping the future developments and direction, including already planned content for Update 1.
Following Jim McKeeth’s recent Embarcadero community post about preparing for Delphi for Linux, I wanted to add a few notes about how you can use Linux today as part of your server architecture; and also point out how to get ready for Linux by using InterBase.
InterBase on Linux
InterBase Server is available for both Windows 32bit and 64bit along with Linux 32bit and 64bit Servers. For Linux, InterBase is certified for a number of distributions including
Because InterBase uses the same On Disk Structure (ODS) you can do your development on Windows along side your favourite IDE (Visual Studio, Eclipse, RAD Studio, Delphi, C++Builder etc) and then copy your application database directly onto a linux machine ready for use.
InterBase – Deeply Embedded on Linux
InterBase ToGo is not currently supported on Linux, however the recent InterBase roadmap includes mention of InterBase ToGo being made available for the Linux Platform in the near future. This will ensure InterBase can be deployed embedded with your application for smaller application usage, as well via the traditional Server Installer for larger scale deployment mentioned above.
Disclaimer: The information included in this roadmap does not constitute, and should not be construed as, a promise or commitment by Embarcadero to develop, market or deliver any particular product, feature or function. The timing and content of Embarcadero’s future product releases could differ materially from the expectations discussed here. Embarcadero reserves the right to change its product plans or roadmap at any time.
It’s been a busy couple of years since the last public roadmap. In that time, the patent pendingChange Views feature has delivered some massive competitive advantage win stories to customers using InterBase XE7 and InterBase was nominated for and won the prestigious IoTA (Internet of Things Award) for “Most Innovative Use of Data”.
Following on from the previous public roadmapInterBase has been on the rise, and here we are sharing the current plans for the next release of InterBase in 2017.
Features and Technologies Delivered in InterBase XE7
64bit Transaction ID’s – Allowing systems with the highest demand to run even longer
New ODS restore feature
Enhanced Journal Archive Management
Service API’s for Online Dump and Journal Operations.
Features and Technologies Expected in InterBase BigBang
This week (15-Nov-2016) at CodeRage the hood was taken off a number of things that have been worked on in the labs for project BigBang. This project will ultimately become the next release of InterBase and includes:
A focus on SQL Features
Common Table Expressions
Truncate Table – A fast way to delete data
Transaction Wait Time
Exclusive Isolation Levels
ISQL scripting enhancements
Faster core engine
Server-wide Performance Monitoring
New Platform Support
Latest Mobile & Desktop
InterBase ToGo on Linux
Ideas for the future.
InterBase releases are based on a specific On Disk Structure (ODS). The ODS helps manage new features and tells the InterBase engine what the database can do and what performance benefits it can take account of. This is one of the reasons is important to backup and restore when upgrading. – But what has this to do with the future?
Making mid-cycle ODS changes is something that we have been very reluctant to do with InterBase in the past because a change to the ODS will prevent you from using the database on an early version. E.g. if Update 2 had a newer ODS, then you would not be able to move back to Update 1 if you wished to. With the changes added for managing ODS in the restore in XE7, we are now comfortable that if we need to, we could move up an ODS during a release cycle. This may pave the way to new features mid-release.
Ideas under review for the future include
Scale Out / Load Balancing
Even Smarter, Faster Engine
More SQL features
Change Views 2.0
Change views working on Views
Option for Backup / Restore (rather than DataDump)
Enhanced Tooling (e.g. IBConsole)
Enhance Drivers for 3rd Party Tools (e.g. More ODBC, JDBC, ADO.Net enhancements)
Coded functions (enabling UDF capabilities with ToGo where platforms do not allow external libraries, e.g. iOS)
In short. no new features, just a few bug fixes to the InterBase core kernel and IBConsole: See full list here
Windows 10 update deletes Files in AppData Directory
Deadlock at database header page when enabling database shadowing
IBConsole does not show proper value for “Page Buffers” in Database Properties form
IBConsole Trigger editor fixes
Change View Subscription causes columns in a group by to be null
Database corruption during fast expansion of single table from multiple clients
Downloading latest InterBase XE7
Embarcadero CodeCentral “Registered Users” can download the patch binaries (Server/Desktop/Developer/Trial) for Windows and Linux, and, ToGo Edition. You can find the downloads at http://cc.embarcadero.com/reg/interbase
The IoT Award Winning database InterBase, has for a long time supported the ability to store data in an array field type. This was originally introduced as a new field type to reduce API calls and speed up data write time for a specific Boeing project many years ago. Writing each value into an array can also simplified the data model as well as benefiting database performance.
While array field in InterBase have been around for a long time, they have not aways been that easy to access from the components layer reducing their adoption.
We (geeks) should all know that applications that run in memory run faster than those that have regular disk I/O.
Having more of the data processing in memory has a positive effect on speed and performance, however its not without risk. As memory is transient, you are always at risk of data loss if the data in memory hasn’t been saved to disk (which is where you get the disk i/o speed degradation again.
InterBase brings together the speed of in memory data processing with the security of immediate disk I/O with InterBase Journaling. The write ahead logging enables InterBase to securely log the write transactions to the journal making the best of both worlds possible.
User Security isn’t new; everyone is use to logging into the applications they use. To help developers build cross platform applications faster, InterBase has a flexible API for user security that simplifies the access to data held in InterBase regardless if your application is deployed to Windows, Mac, Linux, iOS and Android.
User Security in InterBase helps control WHO gets to see WHAT and is enhanced with a strong encryption model (which I covered in the Rising to the Data Security Challenge webinar) so lets focus on the foundations of user security in this article.