dbOrchestra - MySQL - Updates FAQ's
|
| If the update is the file
classes<version#>.jar what do I do? |
| Replace the classes<version>.jar
file in the following location. IMPORTANT NOTE: Close dbOrchestra
before replacing the jar file!
|
| If the update is a zip file what do I do? |
| After downloading the file unzip it to the
dbOrchestra root directory. If you accepted the default when
installing the product this will be...
<drive>\dbOrchestra_MSSQL |
| How do I backup my current version before
applying the updates? |
| Just copy the entire dbOrchestra directory
and its subdirectories to a new location. |
| Can't anyone just download the updates or
software and use the product for free? |
| Without a license key you cannot use
dbOrchestra. |
| How long will you support bug fixes for
previous versions? |
| We will support bug fixes back one major
release version (example, if the current version is 1.6.x, we will
support bug fixes back to version 1.5.x. However, we will only fix
bugs where there is no viable and reasonable workaround to the
bug. |
| Can is use the MySQL license key with
the Oracle and MySQL versions? |
| No. |
| How long can I get upgrades for free? |
| For example, in the current product
release version 1.5.x your license key will work for upgrades
until we release version 1.6.x |
| About how long will that be? |
| We look to release new versions on a 12 to
18 month cycle. |
| Are releases cumulative? In other words I
am on build 003, if I download build 006 will I also get build 004
through 005? |
| Yes. |
| I need to reinstall the entire program?
Where do I get it from? |
| If you still have the original email with
the download url this will get you access to the full package. If
not email us and we will send you the link.
|
| Can I get older releases? |
| We maintain complete source control for
every build that is produced. However, we only maintain the
current build for download. |
