Heh... define "performance". Are you talking speed of code, speed of developing code, speed of testing code, computational ROI, ease of maintenance, ease of use, ease of interface, cost of ownership, speed vs hardware, what???
There are thousands of articles on all the differences and likenesses between the two engines. Just do a web search for (+PERFORMANCE +"SQL SERVER" +ORACLE) or flip it around for (+PERFORMANCE +ORACLE +"SQL SERVER" ). For every article touting the performance of one, you can find an article touting the performance of the other. And, you can find a lot of bad mouthing of both, just as well.
You'll also find that a lot of folks (I'm guilty, too) will write articles or posts on forums about such comparisons favoring one or the other simply because of what they cut their teeth on. It's like comparing the English language to the Russian language... most will gravitate towards whatever their first language is. There are, of course, exceptions to every rule.
There are a couple of things that all databases have in common that you won't find in any tests... crap code and poor database design kills both Oracle and SQL Server. 😉 Everyone tests with optimal or reasonable code... seems like no one tests with crap code to see how bad or how easily a system can be made to bog. 😉
is pronounced "ree-bar
" and is a "Modenism
" for R
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.
"Change is inevitable... change for the better is not".
"If "pre-optimization" is the root of all evil, then what does the resulting no optimization lead to?"
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)