The next major release of Sage 300 ERP (named 2016 but released in 2015) will be dropping support for Pervasive.SQL and Oracle as database servers. This means the only supported database will be Microsoft SQL Server.
The first Windows version of Sage 300 ERP (then called CA-Accpac/2000) supported one database, Btrieve 6.15 – a simple, robust database manager. At that time we had a good bundling deal with Btrieve, so we could include a database engine with every System Manager. Btrieve was a good, low cost database manager that supported transactioning, it was used by many ERPs, and was relatively easy to install and administer. Novell sold off Btrieve back to its original developers and that evolved into Pervasive.SQL.
Unfortunately, however Pervasive.SQL has not really kept up with its competitors. SQL Server now has a free edition and Microsoft is much more favourable to doing bundling deals. Plus, there are now many better low cost database alternatives such as SQLLite and MySQL. Also, over the past years the higher end databases have become much easier to install and manage. Long gone are all the configurable parameters that would plague SQL Server installations. So now Pervasive.SQL isn’t as easy to use.
Although Btrieve was the first database that Sage 300 ERP supported, today it doesn’t seem to have a place anymore.
lot of Sage 300 ERP installations require integrations to many other products, and nearly none of these support Pervasive.SQL. Hence if you want integration with BI tools, or other ERP related software, you are almost always forced to use SQL Server anyway. In the early days of Sage 300, SQL Server was very expensive and most products supported Btrieve as a low cost alternative, but today the need for that has disappeared and we are one of the last Vendors to still be supporting Pervasive.SQL.
We’ve had Oracle support for a while now. However the sales numbers have never really justified the resources required to support this platform. Oracle tends to be the database of choice for larger companies that tend to be bigger than Sage 300 ERP’s target market. We’ve made a few government and large company sales because we support Oracle, but generally these customers would have been as well served by SQL Server.
Our perspective is that the demand for Oracle has waned and that they are really pursuing larger and larger companies and moving further and further away from our market segment.
Multiple Product Integrations
Most Sage 300 ERP sites these days involve multiple products working together. Generally people only want to work with one database system and the common one across the various products is SQL Server. A more uniform experience across all the Sage products really only works well if you choose SQL Server. It’s generally nicer to have just one set up database operations for things like backup. Further when you start to use more advanced cross product reporting tools, these can only do their job if all the products are based on the same database engine (so that SQL joins can work properly, etc.).
The Sage 300 ERP architecture is still the same and supports multiple databases, whether we support another database than SQL Server in the future will depend on the future of the database market. For now we will be concentrating on SQL Server.