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..
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.
answered 07 May '13, 02:29
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 :)