Which ?

[nippleburger]

I have a choice of working with either SQLServer or Oracle within my company. I need to advise them which way to go. I need to support a couple of hundred users in a mixed workload environment (OLTP, Batch & Reporting)
The O/S will be Windows 2003 Server. My understanding is that Oracle is the better database technically but SQLServer is cheaper and easier to integrate with other MS technologies. My company will most likely buy into whatever technology will deliver value for money but also be secure and be able to scale.
Any views gratefully received.

[Xenophon]

Can't help with the question, but congratulations on choosing the most random username I have seen in a while.

What's your password? elbowfries?

[DimPrawn]

Oracle. hugely expensive, complicated, difficult to manage and tune, highly paid DBA's, not Windows friendly, everything is extra, nightmare when it goes wrong.

SQL Server 2005. Cheap as chips, powerful, self tuning and managing, DBA's ten a penny, Windows friendly, .NET built in, comes with OLAP and data mining tools.

Biggest no brainer question this year.

[sasguru]

Oracle. hugely expensive, complicated, difficult to manage and tune, highly paid DBA's, not Windows friendly, everything is extra, nightmare when it goes wrong.

SQL Server 2005. Cheap as chips, powerful, self tuning and managing, DBA's ten a penny, Windows friendly, .NET built in, comes with OLAP and data mining tools.

Biggest no brainer question this year.

yes Oracle is the obvious choice if you're going to be a DBA. Kerchiiing.

[Hex]

I've used both and also Sybase. In your position I would go for SQL Server for all the reasons already given. For 200 users this should be more than adequate. SQL Server is much more user friendly.

[The Lone Gunman]

Peeeeeeeep!!!!

Yellow card gentlemen.

Those answers are far too sensible for the general forum.

Please, you know the rules.

[Xenophon]

Quite right TLG. Everyone please see the response I provided and take note.

[sasguru]

Yellow card gentlemen.

Those answers are far too sensible for the general forum.

Please, you know the rules.

Well the sensible thing is to commit your company to writing a bespoke RDBMS.

[threaded]

I would suggest MySQL. Transactions are only for people who can't code.

[Sputnik]

Can't help with the question, but congratulations on choosing the most random username I have seen in a while.

What's your password? elbowfries?

don't be ridiculous. thats just silly..........