I *almost* agree with you. I would recommend that you look at things on a rule-by-rule basis. If implementing a rule meant making more than a few trips back to the database for additional data, I'd give serious thought to implementing the rule in a stored procedure.

-Mike


>You should not be putting your business rules into SQL Server if you are designing an n-tier solution. That essentially makes it two-tier.
>
>
>>Hi
>>
>>What is SQL-Server's procedural language like? Is it any good to use as a middle-tier?
>>
>>This will be for a complex system where the rules are pretty heavy.
>>
>>Thanks
>>Kev