The forum will experience an outage sometime between February 10 at 7:00pm EST and February 12 at 11:59 EST for installation of security updates. The actual time and duration of the outage are unknown but attempts will be made to minimize the downtime. We apologize for any inconvenience.

asked 11 Nov '10, 19:14

Karim%20Khamis's gravatar image

Karim Khamis
accept rate: 40%

edited 14 Nov '10, 12:01

Volker%20Barth's gravatar image

Volker Barth

For Windows platforms: What are the pros/cons of these installers compared to the Deployment Wizard (which offers to install only client software, too)?

(12 Nov '10, 08:25) Volker Barth

One of the main advantages of the client install for Windows over custom-built deployment wizard installs is that the client install creates a Start Menu folder with icons for DBISQL and Sybase Central. Since it has options during the install, you can choose whether or not to install the administration tools on a machine by machine basis. We will also post EBFs for the client install from time to time.

permanent link

answered 12 Nov '10, 14:18

Bill%20Hillis's gravatar image

Bill Hillis
accept rate: 66%

Comment Text Removed
Comment Text Removed

Bill's answer is more on the pro side of things. One "con" is that the client installer for Windows will give you all interfaces: ADO.NET, ODBC, OLE DB, etc. If you use the Deployment Wizard, you can choose the specific interfaces to deply, as opposed to getting them all.

(12 Nov '10, 15:19) Karim Khamis

Another con is that the client install for Windows includes the JRE used by the admin tools. You can build a much smaller package using the deployment wizard if you don't include the admin tools.

(12 Nov '10, 21:15) Bill Hillis

@Bill: That's an important disadvantage for simple client installs, say in a corporate install where Deployment Wizard setups often are just 3-4 MB small. - IMHO, the main advantage (besides the much broader platform support) is the inclusion of the menus. That's something I have missed in the Deployment Wizard:)

(13 Nov '10, 10:11) Volker Barth

@Bill: Two further questions: 1. Is the created install a "SQL Anywhere standard installation" (i.e. with the original SA product code)? 2. Can it be EBF'ed afterwards? (If so, that were additional differences - and possibly advantages - compared to the Deployment Wizard.)

(15 Nov '10, 11:12) Volker Barth

@Volker: 1. Yes, the install is just a subset of the SA standard installation, so has the benefit of being "guaranteed" to work. By guaranteed, I mean that it has the same bugs as the full SA installer :). 2. It can be EBF's afterwards, but not by the full SA installer. It has a different product code, so requires a separate installer. We haven't posted one yet, but we're working towards having EBFs for the client install as well. They will be smaller because they don't include the JRE.

(15 Nov '10, 14:28) Bill Hillis

FWIW, José has just announced that the Database Client Install has been released for versions 16.0 and 12.0.1:

permanent link

answered 15 May '14, 03:35

Volker%20Barth's gravatar image

Volker Barth
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



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: 11 Nov '10, 19:14

question was seen: 1,919 times

last updated: 15 May '14, 03:35