Home > Archive > SQL Anywhere Feedback > December 2005 > EBF's









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author EBF's
Andrew Braunstein

2005-12-21, 8:24 pm

Allow an EBF to install even if it is older than the current EBF. This only
need work within the same major/minor release. Specifically I would like to
be able to uninstall an EBF, and would be acceptable if this uninstall was
accomplished by re-installing the previous EBF. This is much simpler than
uninstalling and re-installing Sybase. That requires digging up the license
key, installing the release from CD, potentially installing the maintenance
release we downloaded and then installing an EBF.

The overwrite would be much simpler (and likely simple to implement)

--
Andrew Braunstein


Breck Carter [TeamSybase]

2005-12-21, 8:24 pm

I like the idea, but... it would probably make every EBF as large as a
full install.

Let's say EBF 1 does not need to include module A because A is not
changing. However, nobody knows if EBF 2 is going to include module A,
so EBF 1 would have to include it just so it could overwrite the one
that *might have been* installed by EBF 2.

In other words, every EBF would have to include everything... that's
not necessarily a bad thing, it might even make building an EBF easier
for iAnywhere :)

Another approach is to copy the installation folder C:\Program
Files\Sybase\SQL Anywhere 9 before installing an EBF. This works well
in practice; to roll back, one simply renames folders.

In *theory* you should do something with the stuff installed
underneath C:\Program Files\Sybase\Shared but I've never bothered
*and* I've never been hurt by it.

I guess there might also be stuff installed in Windows folders, but
once again, my ignorance has remained blissful.

ON BIG PRODUCTION SERVERS, however, I've always re-installed and
rolled forward... one can never be too paranoid. Plus it's usually a
small blip among all the OTHER CRAP that goes on when you have to roll
back. Plus it almost never happens... that's what all the testing is
for :)

Breck

On 21 Dec 2005 13:19:55 -0800, "Andrew Braunstein"
< abraunstein@healthwy
se.com> wrote:

>Allow an EBF to install even if it is older than the current EBF. This only
>need work within the same major/minor release. Specifically I would like to
>be able to uninstall an EBF, and would be acceptable if this uninstall was
>accomplished by re-installing the previous EBF. This is much simpler than
>uninstalling and re-installing Sybase. That requires digging up the license
>key, installing the release from CD, potentially installing the maintenance
>release we downloaded and then installing an EBF.
>
>The overwrite would be much simpler (and likely simple to implement)


--
SQL Anywhere Studio 9 Developer's Guide
Buy the book: http://www.amazon.com/exec/obidos/A...7/risingroad-20
bcarter@risingroad.com
RisingRoad SQL Anywhere and MobiLink Professional Services
www.risingroad.com
Andrew Braunstein

2005-12-22, 9:23 am

Why isn't it as simple as having a pop-up dialog that says, "Are you sure
you want to apply an earlier version of the system?

When I look at EBF's they are generally the same size, because they do have
to include every module. This is because an EBF needs to include all of the
changes from the GA release to present. Luckily with Sybase, intermediate
EBF's never have to be applied when installing the most recent EBF.

--
Andrew Braunstein

"Breck Carter [TeamSybase]" < NOSPAM__bcarter@risi
ngroad.com> wrote in
message news:1ghjq1t1o9ghd01
775pdhk1ebqjbj23m22@
4ax.com...
>I like the idea, but... it would probably make every EBF as large as a
> full install.
>
> Let's say EBF 1 does not need to include module A because A is not
> changing. However, nobody knows if EBF 2 is going to include module A,
> so EBF 1 would have to include it just so it could overwrite the one
> that *might have been* installed by EBF 2.
>
> In other words, every EBF would have to include everything... that's
> not necessarily a bad thing, it might even make building an EBF easier
> for iAnywhere :)
>
> Another approach is to copy the installation folder C:\Program
> Files\Sybase\SQL Anywhere 9 before installing an EBF. This works well
> in practice; to roll back, one simply renames folders.
>
> In *theory* you should do something with the stuff installed
> underneath C:\Program Files\Sybase\Shared but I've never bothered
> *and* I've never been hurt by it.
>
> I guess there might also be stuff installed in Windows folders, but
> once again, my ignorance has remained blissful.
>
> ON BIG PRODUCTION SERVERS, however, I've always re-installed and
> rolled forward... one can never be too paranoid. Plus it's usually a
> small blip among all the OTHER CRAP that goes on when you have to roll
> back. Plus it almost never happens... that's what all the testing is
> for :)
>
> Breck
>
> On 21 Dec 2005 13:19:55 -0800, "Andrew Braunstein"
> < abraunstein@healthwy
se.com> wrote:
>
>
> --
> SQL Anywhere Studio 9 Developer's Guide
> Buy the book:
> http://www.amazon.com/exec/obidos/A...7/risingroad-20
> bcarter@risingroad.com
> RisingRoad SQL Anywhere and MobiLink Professional Services
> www.risingroad.com



Breck Carter [TeamSybase]

2005-12-22, 11:23 am

FWIW the 9.0.2 upgrade was about 118M whereas subsequent EBFs have
been hovering around 70M... don't think the EBFs contain everything,
just everything that has changed since GA.

Breck


On 22 Dec 2005 07:14:08 -0800, "Andrew Braunstein"
< abraunstein@healthwy
se.com> wrote:

>Why isn't it as simple as having a pop-up dialog that says, "Are you sure
>you want to apply an earlier version of the system?
>
>When I look at EBF's they are generally the same size, because they do have
>to include every module. This is because an EBF needs to include all of the
>changes from the GA release to present. Luckily with Sybase, intermediate
>EBF's never have to be applied when installing the most recent EBF.


--
SQL Anywhere Studio 9 Developer's Guide
Buy the book: http://www.amazon.com/exec/obidos/A...7/risingroad-20
bcarter@risingroad.com
RisingRoad SQL Anywhere and MobiLink Professional Services
www.risingroad.com
Breck Carter [TeamSybase]

2005-12-22, 11:23 am

On 22 Dec 2005 07:58:01 -0800, "Breck Carter [TeamSybase]"
< NOSPAM__bcarter@risi
ngroad.com> wrote:

>FWIW the 9.0.2 upgrade was about 118M whereas subsequent EBFs have
>been hovering around 70M... don't think the EBFs contain everything,
>just everything that has changed since GA.
>
>Breck


Having said that, I still agree with you... a 118M EBF would not
bother me, if it gave me the ability to *safely* roll back to an
earlier EBF.

Breck


--
SQL Anywhere Studio 9 Developer's Guide
Buy the book: http://www.amazon.com/exec/obidos/A...7/risingroad-20
bcarter@risingroad.com
RisingRoad SQL Anywhere and MobiLink Professional Services
www.risingroad.com
Sponsored Links





Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive | Programming forum archive

Copyright 2008 droptable.com