We were surprised and unhappy to learn from Sybase support that if you create an installer with the Deployment Wizard, then you can't simply apply downloaded EBFs. That's a real maintenance inconvenience, especially if we need to apply an EBF quickly. EBFs do a nice job of seeing what you've got installed and only updating what it needs to, so this is was a surprising limitation. Yes, there's are workarounds, but for us they aren't worth it.
Combined with the fact that the Deployment Wizard doesn't support 64-bit installations (and we want to support both) means that we're backing away from the Deployment Wizard.
Too bad. It's a nice feature. I hope that, in the future, these two limitations go away.
FWIW, Dan K.
While I generally agree with your suggestions:
That's what I do to "upgrade" a client installed by a Deployment Wizard package:
I apply the EBF to the "Source box" and then re-run the Deployment Wizard to create the same package as before (i.e. with the same set of options). (That has me lead to ask if those options could not be stored or if the Wizard could be scripted.)
The new package can then be applied to upgrade the clients.
I guess that the resulting package won't be much bigger than a full EBF (and possibly MSM packages might be even smaller - however, I have not used them so far.)
(Sidenote: I have used this primarily to upgrade clients with just client interfaces.)
answered 04 May '10, 07:56
Please, Please - I find this more than an annoyance.
With over 600+ installations, and a support department in many different countries, we want our support staff to make sure clients are running the latest EBF without the aid of the development staff creating EBF's.
EBF's come out constantly, and more importantly, once development moves on to V12, V13, V14 of Sybase, we still need the current EBF to be able to be installed without having to go back and create a deployment.
I honestly believe that Sybase needs to make this happen ... but it should be easy, and you can use SetupBuilder (Lindersoft) to do this - they can do anything.
Simply if the object exists, replace it during an EBF install.
This is a huge issue for us. It needs to be looked at seriously and resolved.
answered 02 Nov '10, 22:42
Look at SetupBuilder from Lindersoft. It is all script driven ... and you have far more control over the installation than any other installation system available.
answered 02 Nov '10, 22:43
FWIW, starting with SA 12, the Deployment Wizard can now be used to create both 32-bit and 64-bit deployments for Windows.
Cf. http://dcx.sybase.com/index.html#1200en/dbprogramming/deploy-s-4228164.html, particularly Jack Schueler's comment.