This is a follow up question to my original SQL Anywhere Client: where is it? question. I recently had the need for an x64 install of the ODBC drivers and the OLEDB drivers for SQL Anywhere 11. I figured all I had to do was run the Deployment Wizard, but I found out that the Deployment Wizard does not have an option to generate a 64 bit msi.
After Googling I found documentation on manual rolling out the client in "dbprogramming_en11.pdf", one of the pdf files that come with SQL Anywhere. The process seems incredibly convoluted and complex. Also, with this method it does not seem like I am generating a neat msi package that I can hand over to our administrators.
Rather than try and program something, I found that the easiest and quickest way to get to where I needed to be was to just install a developers version of SQL Anywhere. At least that got me all the client software installed and registered, but this can't be how the rest of the world does this, can it? And we can't be the first to want to install x64 drivers for SQL Anywhere? What am I missing?
Edit: I just found out that, unlike what the doccumentation says, the SQL 12 Deployment Wizard does allow me to create a 64 bit deployment. Is there any way I can use that to create a SQL 11 deployment (is there even a difference or would it just work?)
I use the 64 bit developer version of 12 to administer our 11 and 12 test databases, but it will not allow me to connect to version 9 dbs.
Unless you need to simulate an all 11 environment, version 12 connecting to 11 will work just fine for administration (in my experience).
answered 27 Jan '11, 14:36
So you are running 64 bit applications (which is still rather rare, methinks)?
In this case I guess Calvin's answer to your original question should work for 64 bit, too, except that you would have to use files from the bin64 sub folder and extend this to use OLEDB files, too, i.e. to include
and to register the first both files, too.
Note: I have not tested this myself, and I'm unaware if there's a 64 bit regsvr32.exe to be used to register these DLLs (as in the odbcad32.exe 32/64 bit confusion)...
answered 27 Jan '11, 15:39