Ok, try that again Alt-S and Shift-S are just a bit too close on this keyboard Actually it has a lot to do with Oracle. Yes, so what Sybase could load a very big DW, what they don't show is when they were doing the queries, what was there transaction isolation level. Default of Sybase SQL Server is "dirty read". That means queries running during that time may not be accurate unless there loader is loading transaction at a time and committing. We don't have that problem with Oracle, so yeah sure they built a big one in a test lab, does it work well in a real world. There is a lot of gaps in the report for my liking to say I really want one of those. Will some managers be going out to install Sybase for a DW now probably, would an Oracle DBA choose it, if the DBA has a say, they would ask some very pertinent questions of query performance during loads, what would be the read isolation to do that i.e. dirty reads. Does Sybase escalates locks during these loads, and what effect does that have on the usability of the product. I think there are good features about Sybase and SQL Server, but for a well rounded product that can perform in all manner of circumstance Oracle beats then hands down. I guess the market generally agrees. So in enlightening us of how to combat bad decisions its good to read and pull apart this for what it is or in this case "Size doesn't matter". I would love to see what Oracle can do on the same hardware Cheers Peter ________________________________ From: David Sharples [mailto:davidsharples@xxxxxxxxx] Sent: Friday, 19 October 2007 07:35 AM To: rajendra.pande@xxxxxxx Cc: exriscer@xxxxxxxxx; oracle-l@xxxxxxxxxxxxx Subject: Re: Worlds largest Data Warehouse ? Whats the point you are trying to make? And what has it got to do with Oracle? On 18/10/2007, rajendra.pande@xxxxxxx <rajendra.pande@xxxxxxx> wrote: No look at the document at http://www.sybase.com/files/Product_Overviews/Ready-Time-Report_R1.2-090 407.pdf