So, you've hinted several times that CoH didn't use SQL Server
I must have been misquoted, because I never said that.
What I did say was that CoH didn't use SQL Server
for static data, such as powers, missions, archetype modifier tables, etc.
It most certainly did use SQL for storage of dynamic data like character records and account data. Though from what I hear it used it rather badly -- simple load/store of entire rows, in some cases loading a full table into memory to query in the code instead of letting the db do it, and lots of unstructured data shoved into text and blob fields. I attribute this to a conflict between NCSoft corporate mandating the use of MS SQL, and the programmers who wanted to store things in flat files (see also the Cryptic Studios "SQL considered harmful" presentation I've linked before). Had there been an actual experienced DBA on staff during the design and implantation process, I suspect things would have ended up quite different.
You know, Codewalker...I'm starting to get the feeling you don't like databases. *grin*
On the contrary, I'm a huge fan of well-designed database schemas and leveraging things like SQL to enable database servers to optimize the queries, manage the caching, and guarantee consistency. The technology is mature and they are very, very good at it. PostgreSQL is my jam.
That said, I have no problem admitting that there are some data structures that relational storage is simply not the best choice for.
*EDIT: Except for MySql. MySql is terrible and if you use it for anything other than a simple read-mostly website, you are bad and should feel bad.
