Bob Leviton
2012-05-15 19:06:51 UTC
Hi,
We deploy SQL Anywhere as the database server for client/server
applications at customer sites. Currently our customers are on SQLA
versions 8, 10, and 11. We are now testing SQLA 12 for upgrade and
deployment at customer sites.
We see that by default, under SQLA 12, when a customer user opens
Sybase Central, ISQL, or SQLA Console, they will in effect be prompted
to install the latest EBF. We don't want this - we need to maintain
control over what version of SQLA all of our customers are using, and
generally only apply an EBF to correct a specific issue that affects
our application. Even for maintenance releases, we don't want our
customers randomly upgrading without being advised by us to do so.
Does anyone have any advice, other than instructing each affected user
to set Update Checker to "never" in all three Sybase apps, and not to
update unless we tell them to?
Thanks,
Bob Leviton
We deploy SQL Anywhere as the database server for client/server
applications at customer sites. Currently our customers are on SQLA
versions 8, 10, and 11. We are now testing SQLA 12 for upgrade and
deployment at customer sites.
We see that by default, under SQLA 12, when a customer user opens
Sybase Central, ISQL, or SQLA Console, they will in effect be prompted
to install the latest EBF. We don't want this - we need to maintain
control over what version of SQLA all of our customers are using, and
generally only apply an EBF to correct a specific issue that affects
our application. Even for maintenance releases, we don't want our
customers randomly upgrading without being advised by us to do so.
Does anyone have any advice, other than instructing each affected user
to set Update Checker to "never" in all three Sybase apps, and not to
update unless we tell them to?
Thanks,
Bob Leviton