Please be aware that the SAP SQL Anywhere Forum will be shut down on August 29th, 2024 when all it's content will be migrated to the SAP Community.

I guess starting with v12, the regular installer does only allow to choose components on a rather high level, e.g. you can choose to install the "SQL Anywhere database" or not, or you can choose to install MobiLink or not.

In older versions and in the according Deployment Wizard of newer versions, you can choose on a more detailed level, say which according client APIs you want to install or whether you would like to install the whole MobiLink suite or just the MobiLink client:

alt text

It would be fine if the regular installer would allow a finer control, too, particularly if one just wants to install some client APIs. Currently I'm tempted to create a MSI file just for these tasks...

asked 12 Mar '14, 05:39

Volker%20Barth's gravatar image

Volker Barth
accept rate: 34%

The options also change, without release notes, with EBFs.

(14 Mar '14, 10:58) vorear2

The regular installer is designed for the developer. We assume that you will be using a variety of components to help develop your application (for example, a database server). Once you get it working, then you deploy your application using the deployment wizard to select only those components needed for your end-user to successfully run your application.

permanent link

answered 13 Mar '14, 08:56

JBSchueler's gravatar image

accept rate: 20%

edited 13 Mar '14, 09:15

Mark%20Culp's gravatar image

Mark Culp


"The regular installed is designed for the developer." That is not a helpful answer. It doesn't even make sense, since it implies that for many years the regular install was NOT designed for developers... or worse, that developers have somehow become stupid (more stupid?) and can't handle choices.

Defaults are great. That's not the issue here.

For example, I recently discovered that a SQL Anywhere installation on my laptop DID NOT HAVE the 32-bit version installed. If memory serves, it was NOT POSSIBLE to choose the 32-bit version during the initial install, but (again, if memory serves) it was available as part of a re-install "modificaton". Not just a minor irritation, but actual lost time resulting in actual lost dollars. Presumably, the assumption was that nobody using a 64-bit OS would want the 32-bit version (ha ha very funny... not).

Over the years the SQL Anywhere setup has become a wonderful component, smooth and worry-free, no doubt the product of Herculean efforts given the complexities created by the Myriad Minions Of Microsoft... you have it right, don't [cough] fix it up :)

(13 Mar '14, 09:28) Breck Carter

Well, for "deloyed solutions" I can follow your reasoning, and I guess everyone will expect (and accept) some effort to put up the deployment here.

However, say, for in-house installations, say, to just

  • install the required database server files (with minimal admin tools) on a server machine or
  • install some client libraries on a MS SQL server box to enable it to connect to a SA database,

that's no real "deployment" IMHO. Here, I would usually just want to start the setup and choose the right options.

To be clear: I guess the Deployment Wizard has become really easy to use - except for the EBF upgrading part and the missing facility to create shortcuts...

(13 Mar '14, 09:50) Volker Barth

Re: "The regular installed [sic] is designed for the developer."

OK, let me rephrase that.

"The regular installer is and always was designed for the developer."

(13 Mar '14, 12:20) JBSchueler
Replies hidden

@Jack: That would still not explain why older versions offered way more detailed install options...

I'd say the installer should as well work for the typical SQL Anywhere part-time DBA, too:)

(14 Mar '14, 04:28) Volker Barth
Your answer
toggle preview

Follow this question

By Email:

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



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text]( "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:


question asked: 12 Mar '14, 05:39

question was seen: 2,258 times

last updated: 14 Mar '14, 10:58