Sybase 9 and Sybase 12 on same server

[Former Member]

Is it possible to have Sybase ASA 9 and Sybase ASA 12 coexisting on the same physical server.

[Former Member]

Thanks for the comments. Are there any issues with ODBC connectivity due to Sybase 12 drivers overwriting Sybase 9 drivers?

[jeff_albion]

No - ODBC drivers are registered underneath individual "ODBC Drivers" entries in the HKLM\\Software\\ODBC\\ODBCINST.INI registry key ("Adaptive Server Anywhere 9" and "SQL Anywhere 12") on Windows, and separate ODBC.INI driver entries on Linux/UNIX.

[Former Member]

Absolutely, even v9, v10, v11, v12 and v16 at the same time. They all install into different directory, by default of course, C:\\ProgFiles\\SQL Anywhere X, and also they all have different env. variables: SQLANY10, SQLANY11 etc.. which makes this happen pretty easily 😉

Just make sure when using utilities like dbinit, that you use the whole path to the correct version of the utility, as they dont include numeric suffix of the version, when compared with i.e. dbsrv12 or dbeng12..

cheers.

[Former Member]

Thanks for the comments. Are there any issues with ODBC connectivity due to Sybase 12 drivers overwriting Sybase 9 drivers?

[VolkerBarth]

No, SQL Anywhere ODBC drivers do not overwrite each other (they are installed in different folders by default and are listed as separate drivers in the ODBC settings). When you define an ODBC DSN, you explicitly choose which driver version you use.

[thomas_duemesnil]

I have used this many times with different versions of ASA. When we upgarde our server we install the new version side by side with the existing one. That way we can run test with the new engine.

What you should be aware of is that some Environment Variables are not version specific. And that when you have batch files the win32 folder is bin32 in ASA 12

Also when you define the services in Sybase Central you will see all Services of all installed ASA Instances.

Otherwise no problem at all.

[VolkerBarth]

some Environment Variables are not version specific

Which ones do you refer to? SQLCONNECT, SQLREMOTE, ...? (These must be set manually, so won't be messed up by an installation, methinks...)

[thomas_duemesnil]

Volker you are right that these variables are not set by Installation. But if you use them they are used for all Instance. SATMP (ASTMP), SQLPATH.

I use SATMP and have not expierienced any problems when to different Server instances use the same temporary directory.

[Breck_Carter]

Good catch, Thomas!

I had the same reaction Volker did ("what the $%@# is he talking about?") but it's true, there are a SACKLOAD of colliding environment variables.

For example, suppose you run SQL Anywhere 12 and 16 side-by-side. Most of the SQL Anywhere environment variables for Version 12 are the same as those for Version 16.

[VolkerBarth]

@Breck: Personally, I can't remember that "what the $%@# is he talking about?" reaction... Nevertheless, the topic may be more subtle and error-prone than expected (by myself) - "WTF":)

[Breck_Carter]

OK, then it was just ME thinking "what the ... " 🙂

[Breck_Carter]

As part of Foxhound testing, I regularly have V5.5, 6, 7, 8, 9, 10, 11, 12 and 16 running on the same Windows 7 box at the same time.

Volker and Thomas have noted the issues, with "dbinit.exe has the same name in all versions" being the only one that has ever affected me.

FWIW V5.5 doesn't like running on Windows 7 very much...

...kind of like running a lawnmower on nitromethane, it runs really FAST for a while and then explodes 🙂

Or...