SQL Anywhere installations are usually identified by version and build; e.g., 11.0.1.2276 where 11.0.1 is the version and 2276 is the build.

EBFs are cumulative within a version number, and each one provides you with a new build for that version. For example, EBFs for version 11.0.0 are cumulative within 11.0.0, and EBFs for 11.0.1 are cumulative within 11.0.1 but separate from the EBFs for 11.0.0.

There are three kinds of deliverables when it comes to building your installation:

• An initial setup.exe for a version, requiring a registration key; e.g., initial setups exist for 11.0.0 and 11.0.1, and they give you the original build of their respective versions.

• An upgrade for moving from one version to another; e.g., if you have 11.0.0 installed (with or without EBFs), you can use the 11.0.1 upgrade to move to the original build of version 11.0.1. Upgrades don't work across major versions; e.g., for moving from 10 to 11 you need an initial setup. Upgrades do include bug fixes, new functionality, behavior changes and updated documentation.

• EBFs update the build within version, as described above. EBFs contain bug fixes but not updated documentation, and they rarely contain new functionality or behavior changes (which would suck, because of the "no updated documentation").

So, to move from 10 to 11, you probably need the 11.0.1 initial setup plus a recent EBF for 11.0.1... or you can use the long road (11.0.0 setup, 11.0.1 upgrade, recent EBF).

I have had good experience with EBFs as far as quality is concerned. After a new version has been around for a while, it is probably a good idea to apply an EBF to get all the initial fixes. After that, EBFs should probably only be installed if they fix a known problem that is affecting you. I.e., I'm still using 11.0.1.2276 which is fairly old, but not as old as the original 11.0.1 build... rock solid, IMO.

SQL Anywhere doesn't have the equivalent of SQL Server service packs, which seem to be more frequent than SQL Anywhere versions but much less frequent than EBFs. FWIW I had to back out an MSS SP not long ago, where "back out" meant uninstall, reinstall and restore database. I am saying that to simply point out that stuff happens with all software products, and you have to be especially careful with DBMS software... testing is a critical part of upgrading.

EBFs are cumulative, so it is sufficient to install the latest. Fully tested are releases which result in a new version number like 11.0.1.