I have a client that is wanting to know the advantages of SQL Server over
Oracle - to be used by in-house developers as the database for custom
applications.
Can anyone provide a few high-level points or links to articles that compare
the products?
Thanks!This has been discussed at length here. Please check archive for the
discussions:
http://groups.google.co.uk/groups?q=oracle+vs+sqlserver
-oj
"Smithers" <a@.b.com> wrote in message
news:e03W%234kCFHA.3368@.TK2MSFTNGP10.phx.gbl...
>I have a client that is wanting to know the advantages of SQL Server over
>Oracle - to be used by in-house developers as the database for custom
>applications.
> Can anyone provide a few high-level points or links to articles that
> compare the products?
> Thanks!
>|||please have a look at the top20 oracle features:
http://www.oracle.com/technology/pu...gdba/index.html
do we have such things in SQL Server?|||It's total cost of ownership is significantly less than Oracle.
The skill level required for a "moderately" effective DBA
to manage the database is less because the tools are far
more intuitive and they are familiar to developers utilizing
Microsoft development tools.
I say that having 5 years of Oracle experience and 5
years of SQL Server experience. Nothing wrong at
all with Oracle. In fact, we use both here at work.
However, for the scenario you describe, I believe
SQL Server is a much better fit.
2005 Microsoft MVP C#
Robbe Morris
http://www.masterado.net
http://www.mastervb.net
"Smithers" <a@.b.com> wrote in message
news:e03W%234kCFHA.3368@.TK2MSFTNGP10.phx.gbl...
>I have a client that is wanting to know the advantages of SQL Server over
>Oracle - to be used by in-house developers as the database for custom
>applications.
> Can anyone provide a few high-level points or links to articles that
> compare the products?
> Thanks!
>|||Not only is it lower now, the TCO gap is going to be seriously affected with
the emergence of multi-core chips. MS SQL counts these as single chips
(therefore no extra cost) but Oracle counts them as multi-CPUs (doubling the
per-CPU license costs). Given Oracle's already huge per-CPU licensing cost,
this is really going to blow the TCO gap even wider.
Regards,
Greg Linwood
SQL Server MVP
"Robbe Morris" <info@.turnkeytools.com> wrote in message
news:eb6J6emCFHA.464@.TK2MSFTNGP15.phx.gbl...
> It's total cost of ownership is significantly less than Oracle.
> The skill level required for a "moderately" effective DBA
> to manage the database is less because the tools are far
> more intuitive and they are familiar to developers utilizing
> Microsoft development tools.
> I say that having 5 years of Oracle experience and 5
> years of SQL Server experience. Nothing wrong at
> all with Oracle. In fact, we use both here at work.
> However, for the scenario you describe, I believe
> SQL Server is a much better fit.
> --
> 2005 Microsoft MVP C#
> Robbe Morris
> http://www.masterado.net
> http://www.mastervb.net
>
>
> "Smithers" <a@.b.com> wrote in message
> news:e03W%234kCFHA.3368@.TK2MSFTNGP10.phx.gbl...
>|||"Smithers" <a@.b.com> writes:
> I have a client that is wanting to know the advantages of SQL Server over
> Oracle - to be used by in-house developers as the database for custom
> applications.
> Can anyone provide a few high-level points or links to articles that compa
re
> the products?
For most in-house apps, either would be fine, and therefore, SQLServer
is probably the better choice because of ease of administration and
out-of-the-box development. IMO, the fundamental difference between
the two is that, in SQLServer, writers block readers and readers block
writers while, in Oracle, writers don't block readers and readers
don't block writers.
In SQLServer, you have code which sort of looks like the following:
Q: Is the row locked?
YES:
- Should I wait for some specific time and retry?
- Go back to the user and let them know?
- Something else?
- Some combination of the above?
NO:
- Okay, let me grab this row so I don't have to go through the
YES steps.
In Oracle, you never have to answer the "is it locked" question unless
two processes are both trying to write the same row.
Other than that, I find them quite similar, but that behaviour is one
that you should definitely understand when choosing between the two.
Galen Boyer
Tuesday, March 27, 2012
Comparing SQL Server to Oracle
Labels:
advantages,
client,
comparing,
database,
developers,
in-house,
microsoft,
mysql,
oracle,
overoracle,
server,
sql
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment