Quote Originally Posted by cjard
Oh come on! We're formatting a date, not putting in a complex BL! SQLserver native way, no .NET hacks, no lengthy T-SQL procedures please! (Similarly, anything that Oracle cannot do that SQLServer can will not be proposed in java, PL/SQL.. )
That [IMHO] is where a big difference comes in in philosophy (again a highly subjective topic).

I tend to look at the comprehensive solution. Eliminating the use of features (and CLR integration is definately NOT a "HACK"...) is simply a device for skewing the results.

Your proposal (to my mind) is the exact same as stating you cant use any command that has an "R" in it (Do you eat oysters? )...

I propose that a fair test would be to (conceptually) setup a client along with a number of DB servers (SQLServer 2008, Oracle, etc). All servers must expose the same functionallity, but one has complete freedom as to the server side of the implementation.

This mimics how most enterprise applications are setup with the two different layers often being designed and developed by independant teams and the ONLY communication between the teams is the API.

The other important thing, is to establish the metrics of what is "better". In business this translates directly to achieving the goal at the lowest possible cost [Total Lifetime].

I will respond directly to your question in my next post...