Re: Losing out to SQL Server
From: Saibabu Devabhaktuni <saibabu_d_at_yahoo.com>
Date: Thu, 21 Feb 2013 15:11:47 -0800 (PST)
Message-ID: <1361488307.21906.YahooMailNeo_at_web161306.mail.bf1.yahoo.com>
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.
Date: Thu, 21 Feb 2013 15:11:47 -0800 (PST)
Message-ID: <1361488307.21906.YahooMailNeo_at_web161306.mail.bf1.yahoo.com>
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
-- http://www.freelists.org/webpage/oracle-lReceived on Fri Feb 22 2013 - 00:11:47 CET