Re: sorry but Oracle v SQLServer again

Jim Kennedy wrote:

> The design tools in SQLserver are not nearly of the same caliber of Oracle
> Designer. (not sure of Sybase Power Designer because I have never used it ,
> but if it is similar to SDesigner then the same statement would hold true
> for Power Designer).
> Jim
> "willy gates" <willy_gates_at_hotmail.com> wrote in message
> news:4344f587.0206060529.1090c0ff_at_posting.google.com...
> > Hello from a bit of a newby
> >
> > I have been through the archives and seen the Oracle vs SQLServer and
> > dont want to start up another fight but....
> >
> > I am going through some costing analysis of a database for out small
> > organisation. I have come down to Syabse ASE, Oracle 9i or SQL Server
> > 2000.
> >
> > From what I can tell SQL server, out of the box, contains all manor of
> > design and profiling tools whereas if I want to design and create an
> > Oracle (or Sybase) database then I need to purchace either Oracle
> > Designer or Sybase Power Designer. I was even told by the Sybase
> > sales chap that I dont even get the DDL with the ASE server, I imagine
> > that the same will be said when the Oracle people get back to me.
> >
> > My problem is that these developer packs are the only thing that is
> > pushing Oracle and Sybase out of my budget, and I would rather run the
> > database on UNIX than NT.
> >
> > David

What Jim says but what you don't say is what you intend to do with it.

If the point is some department level database that has only a few users and can afford to crash from time-to-time or be constantly rebooted SQL Server might be a reasonable choice. If, however, the point is security, stability, scalability, and performance you are definitely working with Oracle or Sybase.

If the choice is Oracle or Sybase part of your decision is the cost of the product. Part of the decision is the in-house skills that your organization already has or hopes to acquire in terms of its long term goals. If your intent is to grow and run a 7x24x365 web site that dictates some of your requirement even if you aren't there as an organization today.

Still another consideration is the depth of resources available to you to support your development efforts. Go to amazon.com and look at how many books on Sybase are available for you to use to support your efforts (56). Perform the search for Oracle (722). Now go to dice.com and look at the resources available to staff your IS/IT effort: Sybase (852 jobs) ... Oracle (4373). One must consider the cost of recruiting and training employees not just the cost of a software license. One must consider the cost of lost productivity due to an inability to find answers to show-stopper questions.

Finally look at the postings in the c.d.sybase versus c.d.oracle usenet groups. The relative strengths of the two communities is pretty easy to discern.

Which leads to the concern that Sybase is a marginal company that may not survive. Do you want to lock yourself, and your organization, into a product that may not be around in the future.

This is not at all an argument that Sybase isn't a good product: It is. But there is more to cost than a software license. And there is more to the decision than what is available right this minute. Two years from now your organization may need more employees (where do you get them) and two years from now you may be looking for another job (and which will be more valuable on your resume?).

Daniel Morgan Received on Thu Jun 06 2002 - 17:20:41 CEST