to revive the Frans vs Rob wars :-)
In the applications my group develops we follow these guidelines:
- use SQL in codebehind classes to VISUALIZE data
- use SPROC to process data (insert, update, delete and transfer)
Why is that? ... because s**t happens
and we value certain DATA/REPORTS more than anything else
Am doing apps for a financial institution interfacing to Accounting, Compliance, Audit and Risk ERP systems with ASP.NET through IE.
In accounting and compliance reporting you are working up to a deadline, trying to report on compliance to some bodies like SEC.
Since everybody is late, data is being processed up till the last minute.
A minute later and your CEO has to ask for forgiveness to a SEC commission,balance sheets are not certified, the company pays a BIG fine, AND YOUR ceo has to take
a flight to ask forgiveness in person.
Despite high availability solutions, best hardware tec etc you can never tell what fails
and we
WANT
to be able to run outr beloved/hated SPROCs by hand, firing up Query Analyzer, a cmd line isql
or a Unix shell with Open Client.
Not performance, but our a** (when the CEO comes back from that trip) is the reason