For clarity and to avoid confusion, since Linux-clusters and Windows-clusters are quite different: An active/passive windows cluster does not distribute load among nodes. A 500GB workload attached to one instance on one node will only have that node to work on. The remaining node will only be for failover. So despite this being a 2-node cluster, it can easily be pictured as a 1-node setup for all practical intents and purposes.
Also SAN backing is required for Windows clusters, and hence can't be avoided. For perspective the amount of actual disks used in this setup was far from extreme. I'm pretty sure we are mostly talking about a few LUNs running something equivalent of RAID5 and RAID0 on regular 10k SAS disks. Nothing fancy.
No schemas were sharded as that completely breaks referential integrity and is something only done in the MySQL-world and essentially kills the ability to do efficient joins. No special features apart from indexing and use of file-groups was enabled, but if disk IO or CPU had been a problem, you could very simply have setup partitioned tables or distributed partitioned views between linked servers to transparently involve more servers and distribute load.
No front-end load-balancing was used, so no client-redirection would be necessary, although Windows clusters allows client-redirection in case of failover. No client configuration apart from the server's cluster-name is needed.
Products used: Microsoft Windows Server 2003 Enterprise Edition and SQL Server 2005 Standard Edition. Cost of these products will most likely vary depending on what kind of existing licensing deal you have and where you live.
My estimate would be that price for this setup is rather insignificant compared to the amounts of data it can seamlessly handle without any developer effort wasted on scaling. No effort what so ever.
Apart from that teenie weenie bit about having an officially supported clustering-setup, I see no reason why you couldn't have used some random Linux iScsi NAS-solution, for instance powered by OpenFiler, which is 100% free.
It also alliviates some of the pains associated with big tables, since MySQL doesn't hava hash-joins and hence has to do row lookups when joining multiple tables. This obviously goes to hell if you are trying to join more than a few rows.
Basically you are not too far off when you say "horizontal partioning", as this (again as far as I have understood it) is a very specific implementation for this.
Basically you partition your data horizontally across multple servers using some predefined/known system and have the client figure out which server it should connect to to get the actual data it needs.
This completely kills the ability to do efficient joins, blows up any ability to sanely implement referential integrity, makes a mess of your code and really has few advantages besides making MySQL able to scale.
People using proper database systems wouldn't know this technique as it is ass backwards in any way you would want to approach databases, is not needed, since most good DBs can handle databases bigger than whatever RAM the server has, not to mention that since it would dislalow efficient joins, this would actually be a way to decrease performance as opposed to improving it.
It sounds like you did not use a SAN or Oracle RAC or anything else which requires exotic and expensive hardware. Please confirm this, and also, if you used non-open-source software, could you provide a ballpark cost estimate?