Re: What Borland should stop wasting their time on

"Jim Cooper" <jcooper@xxxxxxxxxxxxx> wrote in message
news:43df8360$1@xxxxxxxxxxxxxxxxxxxxxxxxx
>
>> I only use stored procedures in my app (SQL Server recommended practice).
>
> I've yet to have anyone explain to me why that idea isn't complete
> bollocks.

It has it's pluses and minuses. I recently worked at a place where we
established a standard that no application would directly execute any SQL
but would call stored procedures for everything. Whether this is a good
thing will vary depending on the way your app is designed.

Good things:
1) Changes and optimizations to databse access do not require a
recompile/redeployment.
2) Clients need only the right to execute stored procedures.
3) Many SQL databases precompile stored procedures to increase performance
4) SQL tasks can be done on request by a DBA who needs not know anything
about programming languages/application programming can be done by
programmers who know nothing about SQL or databases

Bad things:
1) Complex algorithms for building queries are very hard to implement and
nearly impossible to debug when implemented in SQL instead of code
2) Many companies do not version control their database metadata, while they
do versrion control their code
3) SQL is more limited than languages like Delphi, C/C++, etc.


.

Relevant Pages

  • Re: SQL Access security from Window Application
    ... you could have your app handle authentication by emulating the ... Currently my application access the SQL using ... >System.Data.SqlClient and all forms use stored procedures. ... >passwords in a protected file but this creates a problem on remote systems ...
    (microsoft.public.dotnet.general)
  • How do I do Paging through a large dataset via Stored Procedures
    ... Paging by dynamically altering the SQL Query ... Create stored procedures ... SELECT * FROM STUDENTS ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Transaction Oriented Architecture (TOA)
    ... appear to advocate wrapping SQL in OO constructs, ... writing code against the database. ... or perhaps stored procedures as a consolation. ... case or per app. ...
    (comp.object)
  • Re: What Borland should stop wasting their time on
    ... established a standard that no application would directly execute any SQL but would call stored procedures for everything. ... recompile/redeployment. ... about programming languages/application programming can be done by programmers who know nothing about SQL or databases ...
    (borland.public.delphi.non-technical)
  • Re: Help with Stored Procedure
    ... I did mean stuff like system stored procedures (even ... build the query, compile it, and optimize it, then, then this is less ... very not easy using dynamic sql. ...
    (microsoft.public.sqlserver.programming)