RE: Losing out to SQL Server
- From: "Walker, Jed S" <Jed_Walker@xxxxxxxxxxxxxxxxx>
- To: free <oracle-l@xxxxxxxxxxxxx>
- Date: Fri, 22 Feb 2013 15:47:15 +0000
You should have your company consider MySQL. If you're doing OLTP and need it
fast and available.
Sai makes some good points. I've heard a lot of people at my company
complaining about the cost of SQLServer being just as much as Oracle all around.
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Saibabu Devabhaktuni
Sent: Thursday, February 21, 2013 4:12 PM
To: free
Subject: Re: Losing out to SQL Server
WGB,
There are in general more reasons to stay with Oracle for any OLTP application,
that requires availability (99.9 or more) and ability to scale horizontally,
than to be on any other database. As you said, if you believe your application
is better off on Oracle, you may consider looking it options like database
consolidation, implementing ILM, addressing any database performance problems
application may be experiencing to reduce cost of Oracle footprint. This
savings combined with the cost of developers needing to learn new way of
writing sql, T-sql, code it around for read locks, read consistency, etc may
prove that you end up spending more money on Sql server.
The only definitive way to make big decisions like moving to a different
database vendor is by doing a POC with your data and your application, and
clearly demonstrate pros and cons of each database for your use case.
Thanks,
Sai
http://sai-oracle.blogspot.com
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
