Quote:
One interesting thing to note is that with SQL Server 2005 you can use C#, VB.NET and other .NET managed code instead of T-SQL for stored procedures. I haven't used it yet, so I have no idea how well it performs.


Not particularly well. It's very limited in what it can do, awkward in implementation, and damn slow from what I have seen. MS advises using it sparingly.

I don't even see how you can do good BL in the database. Your only real tool is SQL, and that too is very limiting and slow. Too many things require cursors and tons of temporary tables, both of which suck and end up being massively convoluted. You end up doing all the processing on one computer, instead of spreading it around to the client computers. You get a complete lack of UI interaction, because every thing needs to be round-tripped to the database. Not to mention that if your business objects and data tables are exactly the same, you are probably doing something wrong.

There is no reason for their not to be a middle tier just because it is client-server. Logical tiers have only a little to do with the hardware setup, they are about organization of code. For instance, I think BL should be in one place, the more scattered it is the harder it is to maintain, debug, port, and scale. A separate logical tier, even if that tier resides on the client or server machine, is significantly easier to deal with than just sticking your BL in the UI or database.
_________________________
Ninti - MK IIa 60GB Smoke, 30GB, 10GB