Re: Code in the database or middle tier (the CLR controversy)

I don't see any significant consequences with the ability to write stored procedures in C#. As for Dan's comment that C# will lead to bad SQL code -- I see extremely bad SQL code in MSSQL 2000 already. I've seen developers who lovingly comment every method and function of their C++ code but have zero comments in the stored procedures. I've seen stored procedures that exceed 2000 lines without a single comment, not explaining purpose, reason, or functionality. Their attitude is that SQL is a second language to them, while their primary language is OOP. Their development tools, Rational Rose etc., are very sketchy about databases. The way Visual Studio interacts with MSSQL is also something of a Rube Goldberg contraption. I don't see the situation improving or getting any worse with the addition of the CLR into MSSQL 2000. Received on Sat Jun 04 2005 - 09:01:52 CEST