Firebird Versions (Used with Update 242 & 243)
With the imminent release of Update 243 we felt there is a need to explain the use of Firebird Versions and combinations in various scenarios you may experience.
More information will follow specifically relating to the Upgrade process from 242 to 243 along with some new services that will be required in Update 243.
The following points should be noted in relation to Firebird:- We do not recommend Firebird 5 be used with Update 242
- Firebird 2.5 will run with Update 242 and Update 243, however for performance reasons, Firebird 5 is preferable when used with Update 243.
- There may be a point in time (Beyond Update 243) we will require sites to install and use Firebird 5.
- There may be good reasons that a site may choose to retain Firebird 2.5. eg: They may be using Firebird 2.5 ODBC, or have a 3rd party application used with Ostendo that requires Firebird 2.5
By retaining Firebird 2.5, sites can use Update 243, whilst not being forced to Firebird 5 at the same time. The Firebird Upgrade can occur at a later point.
Principally there are three different combinations that can be employed, depending upon the environment and whether previous versions of Ostendo are currently in use.
Firebird 5 Only
Update 243 installed alone on its own dedicated server (Cloud or Local): eg: New Site
If Update 243 is to be deployed on its own server (cloud or local) we will always recommend installing Firebird 5. The reasoning behind this is two-fold:- Firebird 5 will provide better overall performance by managing and balancing CPU loading.
- There are new technology improvements within Firebird 5 that we may wish use in the future with Major Updates beyond 243.
Firebird 2.5 Only
Where Update 242 and Update 243 Co-exist on a Clients Site Local Server:
This configuration would be limited to a site that is considering Update 243 and would like to run both their current Update 242 Live environment alongside an Update 243 test or live environment.
It is suggested Firebird 2.5 be retained unless there is a performance issue, in which case running both Firebird 2.5 and Firebird 5 will be necessary.
Ultimately our recommendation is to use Firebird 5 with Update 243, however sites may still opt to use Firebird 2.5 in this environment if there are good reasons for doing so. eg: They may be using Firebird 2.5 ODBC, or have a 3rd party application used with Ostendo that requires Firebird 2.5
By retaining Firebird 2.5, sites can move to Update 243 without being forced to Firebird 5- In this case Firebird 2.5 would be used for both Ostendo versions.
- Once the site commits to Update 243 and therefore 242 is no longer required, they are not forced to Firebird 5 unless there are performance advantages for them.
- If the site commits to a Cloud server, then our recommendation is that Firebird 5 should be used, but this is not mandatory.
- Important:
- A Cloud Server cannot be used to run Update 242
- Update 242 should only ever be used with Firebird 2.5
- Update 243 can be used with Firebird 2.5
- At a later date, Firebird 5 can be installed to replace 2.5 only after Update 242 is no longer required and there are no further Firebird 2.5 dependencies.
Firebird 2.5 and Firebird 5
Where Update 242 and Update 243 Co-exist on a Consulting Partners Local Server:
This combination would be primarily used in a Consulting Partners environment where they choose to run Update 242 with Firebird 2.5 and Update 243 with Firebird 5 on the same Local server.- This setup would be advantageous for Partners using copies of their clients Update 242 databases for the purpose of testing and development. In this case those Update 242 database copies would be using Firebird 2.5. If they were to access a copy of their clients database that is an Update 243 version, those database copies ‘could’ be using either Firebird 2.5 or Firebird 5.
- In this case the combination of using both Firebird versions will require different ports eg: Firebird 2.5 would use 3050 whilst Firebird 5 may use 3051
- Important:
- Once an Update 243 database has been upgraded to Firebird 5, it can only be accessed by Ostendo using Firebird 5. (Once upgraded to Firebird 5 you cannot move back to 2.5)
- If a database has been upgraded to 243 but still uses Firebird 2.5 it can only be only be accessed by Ostendo using Firebird 2.5 (unless upgraded later for a Firebird 5 environment)
- Update 242 should only ever be used with Firebird 2.5
Partners wishing to use their own cloud server to access copies of Update 243 client databases may need install both versions of Firebird onto their Cloud server.
Summary Of Key Points:
- Update 243 databases will run in a Firebird 2.5 or Firebird 5 environment
- An Update 243 database that has been upgraded to Firebird 5 can only be accessed using Firebird 5
- An Update 243 database that uses Firebird 2.5 can only be accessed using Firebird 2.5
- Update 242 must only be run in a Firebird 2.5 environment
- Once a 243 database has been upgraded to Firebird 5, it cannot be moved back to 2.5
- We are not forcing a Firebird 5 environment only recommending this for performance reasons.
- Care must be taken before committing an existing site to Firebird 5 to ensure there are no existing Firebird 2.5 application dependencies.
- Firebird 2.5 can be upgraded to Firebird 5 at a later stage
- Update 243 can be run on either a Local or Cloud Remote server environment
- Update 242 must only be run on a Local server environment
- Firebird 2.5 and Firebird 5 can co-exist on the same server; however specific Firebird configuration settings are required
|
|
