Well put, Everett.

One may ask whether or not it is good idea to put all the business logic in the application, when a company decides to move from a Java application server to a Microsoft .NET platform.

Businesses may well desire better portability of the application rather than the database, so the better choice would be to keep the business logic in the database. Others want to support several databases, and decide to put the logic in the application.

Oracle has supported object oriented programming in the database for years, first with PL/SQL and then with Java. Microsoft has finally caught up and now enables us to do some sophisticated programming in the database, _if_ we want to. Some systems that I've worked on use that Oracle capability and some don't. It will be the same for applications on Microsoft SQL Server.

If we split the "business logic" into validity/integrity, common must-have business rules, application/work flow rules, and user specific rules, then the placement of the logic should be obvious. That still needs analysis to classify the requirement but its a lot clearer.