We are about to flip the switch and upgrade from SQL Anyhwere 5.5 to 11. Our clients connect through ODBC to the database server, so I need to roll out SQL Anywhere ODBC client drivers so I can set up system DSNs in ODBC. My problem is that I can't find the client anywhere.

I can install the complete software on a machine, and I have actually done that for testing, but I don't want to roll out DB management tools to every user in our organization.

Where can I download "just the client" for SQL Anywhere 11?

asked 10 Dec '09, 18:29

RobertDD's gravatar image

RobertDD
489161719
accept rate: 42%

edited 04 May '10, 07:56

Volker%20Barth's gravatar image

Volker Barth
30.6k306456663


In your development machine, run the Deployment Wizard (Start > Programs > SQL Anywhere 11 > Deploy SQL Anywhere for Windows). That will launch the wizard where you can select only to deploy the ODBC interface (uncheck everything else). When the wizard ends, you'll get an MSI file that you can use to install the client.

José

permanent link

answered 10 Dec '09, 18:50

Jos%C3%A9%20Ramos's gravatar image

José Ramos
1.0k51524
accept rate: 30%

That is the trick! Thank you

(14 Dec '09, 16:30) RobertDD

You can also grab 4 DLLs from one of your installations: (C:\Program Files\SQL Anywhere 11\win32)

  1. dbodbc11.dll
  2. dblib11.dll
  3. dbcon11.dll
  4. dblgen11.dll

Then on each client machine, register (regsvr32) dbodbc11.dll

I do it this way because I package this into our own application's install packages.

Works well for us...

permanent link

answered 10 Dec '09, 23:34

Calvin%20Allen's gravatar image

Calvin Allen
1.5k232638
accept rate: 25%

Comment Text Removed

I suppose ...win32 should read ...Bin32. Things are changing from what they used to be in them good ol' days.

(11 Dec '09, 16:32) Reimer Pods

Ah, did not know that (we're still using 10.0.1), thanks for the info!

(11 Dec '09, 19:39) Calvin Allen

The dbclient.exe executable ceased to exist in Version 6, replaced with a "compatibility utility" dbcli6.exe which, in turn, ceased to exist in Version 7, not replaced.

Soooo, that answers your first question, "where is it?" Other folks have answered your next question, "what do I do now?".

Sadly, with Version 10, someone made the incorrect (IMO) decision to remove the following section from the Help. If you think any of this material might help you, I can post it; note that it was written for the leap from 5.5 to 9, and there are other sections in the V11 Help that talk about upgrading (everything changed in V10).

===== From the V9 Help...

What's New in SQL Anywhere Studio

Upgrading Version 5 Applications

About this chapter

The client/server communication protocol changed between SQL Anywhere version 5 and Adaptive Server Anywhere Version 9. This chapter provides upgrade instructions for those users upgrading from Version 5 to a newer release of the software.

This chapter describes upgrade procedures that apply to the change in communication protocol for users of SQL Anywhere Versions 5.0 and 5.5, and users of Watcom SQL 4.0. In particular, it addresses the problem of stepwise upgrades of client/server installations.

  • Understanding version 5 upgrades
  • Review of SQL Anywhere Version 5 architecture
  • Upgrading embedded SQL applications
  • Upgrading ODBC applications
  • Using the compatibility library
  • Capturing dbclient command information
  • Upgrading databases
  • Upgrading version 5 SQL Remote installations
permanent link

answered 11 Dec '09, 14:00

Breck%20Carter's gravatar image

Breck Carter
25.8k428592853
accept rate: 20%

Here is a link to the online version of the version 9.0.2 docs if someone wants to still get that info but doesn't have the V9 installed. http://www.ianywhere.com/developer/product_manuals/sqlanywhere/0902/en/html/dbwnen9/00000152.htm

(15 Dec '09, 22:30) Chris Kleisath

In addition to what others have said, I am very glad that the dbclient.exe ceased after V 5.5. We have a legacy system (3rd party software) still running on V 5.5.05, and when connecting to the server from a client machine, dbclient.exe is often enough shutting down the connection when it isn't supposed to do so.

So, for me, the decision to put the client communication stuff in the DB interface DLLs in V 6 and above (and to support ODBC as an native interface) is undoubtly a really good one:)

When running on 32-bit Windows, I second José's recommendation to use the Deployment Wizard. Besides the ease to extract only the necessary client files (which will result in a small MSI file of only a few MB), it's really easy to redo the setup in case you want to switch to a newer build – so keeping several clients on a current build level is not much afford.

permanent link

answered 12 Dec '09, 21:24

Volker%20Barth's gravatar image

Volker Barth
30.6k306456663
accept rate: 32%

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
×21
×14

question asked: 10 Dec '09, 18:29

question was seen: 8,848 times

last updated: 04 May '10, 07:56