On Thu, 5 Dec 2002, Brian Knox wrote:
> Speaking from the perspective of a long time postgresql user, who
> currently has several very mission critical applications using postgresql
> on the back end, at a very large company...
>
> I can say the one consequence of the problem that I have run into
> personally, is convincing management to allow me to use postgresql for my
> projects to begin with. Fortunately, where I am currently employed, I was
> able to bash my head against the brick wall until they got tired of
> hearing from me, and allowed me to go with postgresql instead of sybase
> (which was their first choice, as the corporation already has a sybase
> site license).
>
> The lack of name recognition was a factor that contributed to the
> difficulty of getting postgresql accepted. The last thing a non technical
> middle manager wants to tell his or her manager is that some mission
> critical application that just crashed was running on some database he had
> never heard of before that he gave the go ahead to use.
Not name recognition, but it'd be nice to think that's the reason.
Mysql has alot of name recognition but you didn't mention them. You
mentioned sybase and having a sybase site license. Marketing wouldn't
help here, they want a commercial database used that they've already
paid for.
What too many people fail to realize is that in a commercial environment
many companies want another company to point the finger at in case of
disaster. Sybase failed, or HP failed, or IBM failed, or Microsoft
failed. They feel they can do something about that. If they lose a
few million they have someone they can go after, who are they going to
go after if PostgreSQL fails them? Marc? Bruce?
Vince.
-- Fast, inexpensive internet service 56k and beyond! http://www.pop4.net/ http://www.meanstreamradio.com
http://www.unknown-artists.com Internet radio: It's not file sharing, it's just radio.