Comments on: Oracle or SQL Server White Paper http://arnoldit.com/wordpress/2009/07/18/oracle-or-sql-server-white-paper/ by Stephen E. Arnold Thu, 24 May 2012 16:47:40 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: Dynamics GP California Partner Notes: how not to use SA account in Great Plains administration | Web & online Software Development http://arnoldit.com/wordpress/2009/07/18/oracle-or-sql-server-white-paper/comment-page-1/#comment-64242 Dynamics GP California Partner Notes: how not to use SA account in Great Plains administration | Web & online Software Development Fri, 14 Aug 2009 09:17:35 +0000 http://arnoldit.com/wordpress/?p=7130#comment-64242 [...] Oracle or SQL Server White Paper (arnoldit.com) [...] [...] Oracle or SQL Server White Paper (arnoldit.com) [...]

]]> By: humble me http://arnoldit.com/wordpress/2009/07/18/oracle-or-sql-server-white-paper/comment-page-1/#comment-60852 humble me Sun, 19 Jul 2009 21:51:07 +0000 http://arnoldit.com/wordpress/?p=7130#comment-60852 This is just my experience: We have built a .Net system based on sql server. and later, ported it to Oracle. my observations: 1) You need 10 times more time and knowledge to build in Oracle. 2) everything in Oracle is tunable. It is very easy to make a mistake that will kill your performance. Oracle will not tell you when you make the mistake. 3) There are small things like 31 characters names, and uppercase letters, that make the schema suprisingly unreadable. 4) I could tune my 1000 users system with the suplied profiler. Oracle needs a real expert to get not much better results. 5) managing stored procedures was much simpler than in Oracle. 6) Oracle locking is much much better than MS sql locking - this is critical for big systems. for a system like the one we built (about 60 man years, 1000 on-line users, 0.5 TB data) - sql server costs millions less to implement than Oracle. This is just my experience:
We have built a .Net system based on sql server. and later, ported it to Oracle.
my observations:
1) You need 10 times more time and knowledge to build in Oracle.
2) everything in Oracle is tunable. It is very easy to make a mistake that will kill your performance. Oracle will not tell you when you make the mistake.
3) There are small things like 31 characters names, and uppercase letters, that make the schema suprisingly unreadable.
4) I could tune my 1000 users system with the suplied profiler. Oracle needs a real expert to get not much better results.
5) managing stored procedures was much simpler than in Oracle.
6) Oracle locking is much much better than MS sql locking – this is critical for big systems.

for a system like the one we built (about 60 man years, 1000 on-line users, 0.5 TB data) – sql server costs millions less to implement than Oracle.

]]>