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?)

asked 27 Jan '11, 14:03

RobertDD's gravatar image

RobertDD
489161719
accept rate: 42%

edited 27 Jan '11, 14:16

Just in case you already have licenced SA12 - of course then you could use a SA12 client to connect to a SA11 server, and could really use the SA12 64 bit Deployment Wizard. Just in case...

(27 Jan '11, 15:41) Volker Barth

@Volker: What would the minimum license ($-wise) be that I need to pull that off? Is a developer's licence enough?

(27 Jan '11, 17:46) RobertDD

@Robert: I'm whether part of the iAnywhere staff nor in sales, so I can't tell. But see my comment on my answer: I guess a 32 bit install should be sufficient.

(27 Jan '11, 22:02) Volker Barth

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).

permanent link

answered 27 Jan '11, 14:36

Siger%20Matt's gravatar image

Siger Matt
3.2k516998
accept rate: 13%

As I understand, Robert wants to use 64 bit clients apps, not administration tools. Just my undersatanding:)

(27 Jan '11, 15:53) Volker Barth

@Volker: Yes, that is correct. I want to connect our in-house written Delphi programs through ADO (OleDB) and ODBC to SQL Anywhere.

(27 Jan '11, 17:41) RobertDD

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

  • dboledb11.dll
  • dboledba11.dll
  • dbelevate11.exe

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)...

permanent link

answered 27 Jan '11, 15:39

Volker%20Barth's gravatar image

Volker Barth
31.5k318461676
accept rate: 33%

Comment Text Removed
Comment Text Removed
1

With regsrv32.exe MS introduced the same naming confusion as with odbcad32: %WINDIR%System32regsvr32.exe is for 64-bit dlls, while %WINDIR%syswow64regsvr32.exe handles 32-bit Files. Otherwise you'll get error messages.

(27 Jan '11, 16:52) Reimer Pods

I am NOT running 64 bit apps, just a 64 bit OS. I still need a 64 bit installation as the generated 32 bit msi generated by the deployment wizard does not work!

(27 Jan '11, 17:45) RobertDD

@Robert: AFAIK a 32 bit app running on a 64 bit OS still needs its DB client APIs in 32 bit. Therefore a Deployment Wizard generated 32 bit client API install should do (and does in my case).

(27 Jan '11, 22:01) Volker Barth

@Volker: Interesting. In all the experimenting we did to get things to work, and after your comment, I am now unsure if I actually saw the 32-bit client fail, or if I drew a wrong conclusion along the way. We will give installing the 32-bit drivers a go before we try anything else. I will report back!

(28 Jan '11, 14:56) RobertDD

@Volker: I have generated the 32-bit msi, both from a 32 bit and a 64 bit platform, and tried to install it on the 64-bit server. I do not see my SQL 11 ODBC driver when trying to add an odbc datasource. When I install the developer version it is right there. When I run that same msi on a 32-bit platform it is right there as well. Disappointed...

(31 Jan '11, 20:59) RobertDD

@Robert: Are you sure to use the correct 32-bit version of the ODBC administrator, i.e. %WINDIR%syswow64odbcad32.exe (see Reimar's comment above)?

(31 Jan '11, 21:57) Volker Barth

@Volker: With the msi I do not really get to choose what regsrv gets used. And when I installed the msi, and then manually afterwards registered the 2 dlls with the regsrv32 in the syswow64 dir it also did not work. I really do not understand why there isn't just a no-hassle standard install available that just installs all available client protocols (ODBC, OLEDB, ADO.NET, JAVA, etc) for x64.

(01 Feb '11, 21:58) RobertDD

@Robert: I have just taken a 32-bit 11.0.1.2376 install with just the ODBC/OLEDB client APIs (created on a 32-bit system with the Deployment Wizard), and installed it successfully on a 64-bit Windows 7 system. All ran fine, all is installed/registered correctly in the 32-bit subsystem, the ODBC entries only show up in the Wow6432Node of the registry as expected. So it generally should work without hassle (and doesn't need any manual intervention or registration). - You might ask technical support for more information/help...

(02 Feb '11, 09:20) Volker Barth
More comments hidden
showing 3 of 8 show all flat view
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×24
×22
×15

question asked: 27 Jan '11, 14:03

question was seen: 7,246 times

last updated: 27 Jan '11, 15:39