Can I install two setups of the same major version on the same box?

[VolkerBarth]

Like many others, I have routinely used several major SQL Anywhere versions in parallel on the same boxes. Besides the need for a particular base directory for each version and the care to take when using the database utilities (%ASANY8%\\win32\\dbinit, %SQLANY10%\\win32\\dbinit ...), I have never run into problems.

But what do I have to take into consideration when installing two setups of the same major version on the same box? - For example a full 10.0.1 install and a 10.0.1 OEM setup (both on the same EBF level, the latter being created with the Deployment Wizard)? - Is this a supported install?

I'm asking because the following seems to happen (running WinXP 32 bit):

• Each version is installed into its own directory (they must be different, obviously). So far, so good.
• There is just one set of environment variables (SQLANY10 and the like), and they seem to point to the last install. The PATH variable contains both directories now.
• As the OEM install uses a different ProductCode than the full version, there are two different products in the Software panel to deinstall. Unfortunately, both are namend very similar ("SQL Anywhere 10" vs. "SQL Anywhere 10, Software" - the latter being the full version).
• As the ODBC drivers have the same name, they point to the last install, too.

As I have installed two versions with the same EBF level, everything seems to run fine.

But are there further CAVEATS to expect?

(Sidenote: I'm aware that SA12 has improvements to include OEM ODBC drivers and a user-defined product name to be specified in the Deployment Wizard, so these issues can be resolved with SA12.)

[VolkerBarth]

Is there any official recommendation?

[Former Member]

Volker... If this is a test/dev machine, perhaps a virtual machine environment help you? I have a friend that uses a bunch of instances of VirtualBox to test web sites under different versions of MSIE- which allows only one version to be installed. He's got a VM set up for every version of MSIE.

[VolkerBarth]

A virtual machine is a reasonable suggestion, for sure. And for general testing, I would certainly choose that road. - In the actual situation, however, I'm gonna live with both installs on my dev box, as this is easier to handle.

I'm still interested in an official statement - or am I the only one who has ever tried such a setup? Don't think so:)

[Former Member · Accepted solution]

I'd like to provide the official answer: we DO NOT support installing different editions of the same major version of SQL Anywhere on the same machine. For example, if you install the Developer Edition of SQL Anywhere 12, and then install the Authenticated (OEM) Edition (also of SA12), you will end up with the OEM Edition, not both.

If you want to change the type of edition you have (e.g. from Developer to Authenticated), just use the dblic utility with the -k command line argument. Note that this is only valid of SQL Anywhere 12 and higher. If you use earlier versions, you must either (1) use a conversion registration key (according to your license agreement) or (2) uninstall the current edition and re-install the edition you want.

Note that we DO support installing different versions of SQL Anywhere on the same machine. For example, you can install SQL Anywhere 10.0.1, 11.0.1 and 12.0.1 on the same computer.

[VolkerBarth · Accepted solution]

OK, so I'm on my own risk, as expected:) But it's good to have an official answer here.

[MarkCulp · Accepted solution]

Note that Jose's answer applies to Windows install... The unix (e.g. Linux) install allows you to install SQL Anywhere in any directory and therefore you can install multiple copies of the same version (or any version) on the same host.

[VolkerBarth]

Well, one thing to beware:

I just de-installed the second setup (the OEM one), and now the SA 10 ODBC entries are gone, as well (whereas I had expected them to be left, pointing to the full install). SA 10 environment variables are gone, too, whereas the PATH variable is left unchanged (i.e. including paths for both setups).

Not sure whether this is due my particular OEM setup, and all will be fine if I re-install the OEM setup but somewhat unhandy nevertheless...