FreeLists / oracle-l / Re: Oracle vs SQL Server

["Stefan Knecht" <knecht.stefan@xxxxxxxxx>]

Hi Sandra,

if price is an issue, consider taking a look at Oracle10g Express Edition -
it's free.

The limitation (theoretical) is that you can't store more than 4GB of data
inside the database, and allocate no more than 1GB of SGA (RAM for the
database). If you're ok with that - nothing's stopping you to stick with
Oracle.

Aside from that, PL/SQL is strictly Oracle. Microsoft SQL Server won't be
able to "understand" that. All the stored procedures have to be rewritten -
and I'm not even sure (but perhaps somebody else knows more about that) that
SQL server has a  built-in procedural language.

But basically, the more of the functionality of a database you're using -
the harder it becomes to port the app to another database.

Anyway, check out Express Edition - it might just be what you (or your boss)
is looking for

Stefan

On 10/1/06, Sandra Becker <sbecker6925@xxxxxxxxx> wrote:
> My boss believes that if Oracle can't come down in price to that of SQL
> Server, we should just switch.  I have never used SQL Server so I had
> nothing to draw on other than what I've heard.  We're a small company with
> limited financial resources, but I believe the decision should be based on
> more than strictly price.  To that end I have three questions.
>
> 1.  Is there an article comparing either 9i or 10g (currently on 9i
> Standard One Edition preparing to migrate to 10g Standard Edition) with SQL
> Server
>      2005?  We run on RHEL3 and will be moving to RHEL4 within then next
> month or so on a Dell 64 bit dual core server.  I have reviewed the articles
>      mentioned on Tom Kyte's website, but nothing did a comparison of
> Oracle and SQL Server 2005, which is the release my boss is considering.
>
> 2.  I know absolutely nothing about Java code.  We develop and deploy Java
> code for a very specific application for a specific industry.  The code uses
>      PL/SQL procedures and sequences extensively.  It also uses a db_link
> to move data from production to a demo database for our new customers and
>      for demonstrating new features for current customers.  What might be
> involved in changing the code?  Would it need to be changed at all?
> Obivously,
>      it would have be tested under load.
>
> I would appreciate any information that will help us make an informed
> decision rather than a knee-jerk reaction to pricing structures.
>
> Thank you.
>
> Sandy