Re: architecture question

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Wow, flame on here.
Generally people who don't listen/admit mistakes/take advice are hard to
work with, and under... I know little compared to some of the flyers around
here, but it's that admission that keeps us current/fresh/growing.

"Jon" <Jon@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23DimES8vHHA.4612@xxxxxxxxxxxxxxxxxxxxxxx
I'm working on a project and the lead developer wants to put all of the
business logic on the database side. He wants the proc to do all of the
logic and create XML on the fly, parse out data, etc, and then return the
final result to the business layer. I pushed back and said that the
business layer should do all of the logic, just have SQL return the data
needed and then have the code do all of the XML creation, parsing of data,
etc. I was told I was wrong and thats not the best practice.
Now, this app can hit the db by a total of 100-500 users a day, and having
the db do all of the processing can have a performance hit. Then he
mentioned something about using temp table in the database side, do a
select, then insert into the temp table, then do a select on the temp
table and do the business logic. I pushed back on that as well..

Now, I'm not a DBA but a developer and I've seen DB's take performance
hits when doing logic such as this on the database side, so my question
is, which would be the best solution for this?




.

Relevant Pages

  • architecture question
    ... I'm working on a project and the lead developer wants to put all of the ... business logic on the database side. ... the db do all of the processing can have a performance hit. ... select, then insert into the temp table, then do a select on the temp table ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: architecture question
    ... because the database is better at handling those kinds of operations. ... think the XML generation and the whole temp table business is garbage, ... logic and create XML on the fly, parse out data, etc, and then return the ... Now, this app can hit the db by a total of 100-500 users a day, and having ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: architecture question
    ... On this particular server, we will be running up to 30 or so different ... database for 20 different applications. ... be happy as your DB wil be hit more than necessary. ... select, then insert into the temp table, then do a select on the temp ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Temp tables vs Permanent table with deletes
    ... Table expressions are literally inline macros, the SQL is expanded into ... using a persistent table for my temp storage - something surprising to ... many programmers who are used to CPU bound tasks that _always_ run ... an application database rather than tempdb. ...
    (microsoft.public.sqlserver.programming)
  • Re: Temp tables vs Permanent table with deletes
    ... CTE the optimiser hasn't a real idea in most cases (given real world SQL) how many rows will be returned on the intermediary steps, so you get a general plan. ... The worst 'improvements' come from doing things like avoiding the table creation overhead by using a persistent table for my temp storage - something surprising to many programmers who are used to CPU bound tasks that _always_ run faster if I do less work here;) ... Using a permanet table to act as a temporary table just causes blocking, fragmentation and additional logging because people usually locate it in an application database rather than tempdb. ...
    (microsoft.public.sqlserver.programming)