Timeline to applying Sybase (ASE) EBFs

Possibly this is a mis-use of this area, we'll see.

I have a client who has asked Sybase to tell them about typical take-up rates for a new ASE EBF on the latest maintenance release.

ie. when a new ASE EBF is released, how many sites will have put this into DEV, TEST & PROD after 1 week? 2 weeks? 1 month? 3 months?

The client is looking for some conservative figure to say "we will wait this long before we believe the EBF is not a dud and is worth some testing effort".

I personally think that magic number is probably 2 weeks, since I do remember once (in 13 years) Sybase recalling an ASE EBF, and they recalled it within a week.

Anyway, they've asked me and I'm asking you for any stats or anecdotal figures you might have. Sybase have said - reasonably! - that they can only infer this based on version strings reported when cases are raised.
LVL 24
Joe WoodhousePrincipal ConsultantAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Joe WoodhousePrincipal ConsultantAuthor Commented:
To clarify, I'm looking for anything at all anyone can say here:

"In the last ten sites I've worked at, it took about an average of a month to get a new EBF into test, and three months into Prod"

or

"we seldom saw the latest EBF until it was no longer the latest EBF, often by months"

or

"we have a strict policy of upgrading our standard dev/test build every quarter to whatever the latest patches are for the OS and Sybase"

or...?
0
grant300Commented:
Joe,

Unfortunately, many of the SMB Sybase sites I have dealt with in the last few years have taken an "if it ain't broke, don't fix it" approach to EBFs.  Oracle sites are a different story....

One of my clients develops software and ships it to customers who test, integrate, and eventually deploy it.  The cycle between start of development of a new release and actual deployment can be as long as 18 months.  As a result, I got them to go from 12.5 0.x to 12.5.1 several years ago but only because it was not stable on the version of Linux they were running on.  I tried for almost three years to get them to "upgrade" to 12.5.4 but that was considered and "upgrade" so they were afraid of it.

It wasn't until a combination of feature requirements and the customers asking about using the "free" Sybase Express edition that they agreed to upgrade to ASE 15.0.2 for a release that is in the works now.  They way the CM folks and I decided to handle database versions from now on is to only specify the major and minor release numbers and treat everything else as "patches"; e.g. 15.0  This way when 15.0.3 comes along, we can move to it and still call it 15.0

To be honest, I not sure I would apply every EBF that comes along.  If my system is stable, performing well, and I am not running into or potentially running into any of the bugs the EBF repairs, I am hard pressed to find a strong case to fool with things, particularly production.  I might role them into DEV on a routine basis if only to figure out if they have any real impact and test them before they get to a critical system, but I would be more inclined to figure on upgrading DEV, TEST, and PROD at double-dot releases and apply EBFs on an as-needed basis.

FWIW,

Bill
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Joe WoodhousePrincipal ConsultantAuthor Commented:
Thanks for some feedback!

Anyone else? Between the regulars here we must know about quite a few sites!
0
Cloud Class® Course: Certified Penetration Testing

This CPTE Certified Penetration Testing Engineer course covers everything you need to know about becoming a Certified Penetration Testing Engineer. Career Path: Professional roles include Ethical Hackers, Security Consultants, System Administrators, and Chief Security Officers.

Joe WoodhousePrincipal ConsultantAuthor Commented:
Anyone else? Was really hoping to see a comment from all the regulars here...
0
Jan FranekCommented:
Hi Joe,

we have no systematic approach.
Basicly there are two scenarios:
1. If we experience the problem probably repaired by EBF, then we apply EBF as soon as possible.
2. If we don't see any problems, we don't apply EBF until HW upgrade. At that point we usually google up latest EBF for reported problems. If we don't see any problem reports, we apply latest EBF.
0
Joe WoodhousePrincipal ConsultantAuthor Commented:
Hmm. Interesting. Thank you.

Anyone else? 8-)
0
Joe WoodhousePrincipal ConsultantAuthor Commented:
Thanks for sharing. I was hoping for more responses but EE is nagging me to close this. 8-)
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Sybase Database

From novice to tech pro — start learning today.