Re: MS SQL Server vs Oracle, MySQL or MongoDB

  • From: "Yong Huang" <dmarc-noreply@xxxxxxxxxxxxx> (Redacted sender "yong321@xxxxxxxxx" for DMARC)
  • To: "fuzzy.graybeard@xxxxxxxxx" <fuzzy.graybeard@xxxxxxxxx>
  • Date: Sat, 30 Aug 2014 12:22:59 -0700

Hans,

Any pointer would be appreciated. Note that I'm talking about parsing overhead 
in Oracle vs. SQL Server. I don't see the connection to transactions or 
resource management in general, which would be an interesting topic but 
irrelevant here.


Yong Huang


--------- original message ---------


On 29/08/2014 9:21 AM, Yong Huang (Redacted sender yong321@xxxxxxxxx for 
DMARC) wrote:
> Reading Jonathan's blogs on SQL Server reminds me of Laimutis's old
> question: Why is SQL statement parsing a big issue to Oracle but not to
> SQL Server?
> //www.freelists.org/post/oracle-l/Any-reason-not-to-have-logic-in-the-db,17
>
> That's a great question and I'd love to hear some comments.
That question has been around for several decades and has created some 
very amusing and heated flame wars, especially in CDOS.

But it does tie to 'what is a transaction' and how the different engines 
handle transactions as well as 'what is resource management' and how do 
the different engines manage resources.

Other related posts: