Comments on: Stored Procedures vs Ad Hoc SQL

By: sunglass hut

sunglass hut — Mon, 31 Oct 2011 09:22:10 +0000

I know, I always live in the memories, I know, I always remember the past, I know, forget you have to forget.

By: christian louboutin

christian louboutin — Sat, 02 Apr 2011 08:57:49 +0000

http://www.fashionchristianlouboutinshoes.com/
christian louboutin is the symbol of women.
It is said that a woman without christian louboutin sales knows nothing about fashion.
That is right.If you want to be fashionable.Please christian louboutin shoes.

By: current affairs

current affairs — Fri, 01 Apr 2011 05:40:13 +0000

Excellent post. I’m actually surprised the use of blogs and wikis isn’t higher.

By: web marketing melbourne

web marketing melbourne — Tue, 21 Dec 2010 04:53:02 +0000

There is an argument I didn’t find in your article: by implementing (some or all of) the business logic in stored procedures, you allow to reuse that business logic from *all* the layers above. In some cases, that can be extremely useful. I work on medical applications that always have to integrate with some legacy code, sometimes running on very exotic platforms/environments. Tough (or impossible) to call .NET/COM/whatever code running on a middle tier from there, but usually OK to call SPs directly. Having most of the business rules at the database level ensures that whatever the call context (from middle tier or from a legacy application), the same rules will apply.

By: website design hampshire

website design hampshire — Sat, 18 Dec 2010 08:53:31 +0000

When dealing with the maintenance issue, having a central location for dealing with data and only data, increases the ease of maintenance. Let’s take for instance, calculated data (cola + colb / colc). In an ad hoc situation, your calculation is created and ran by the user / application. Each user / application could calculate the same metric differently (both (cola + colb) / colc or the previous example). Whereas, sprocs (or even views) help eliminate that problem. Additionally, should the calculation be wrong, you no longer have to update the application, you only have to update the sproc. Because remember, when you update the application, you then have to deal with redeployment of that app.

By: Corwin

Corwin — Thu, 26 Jul 2007 19:06:52 +0000

You can create test harnesses to test/debug the procs. And if you include tons of commmented out tests in the harness, you can easily retest portions as needed. Stored procs should contain an error handling routine that passes back something better than 512.

Embrace it, logic in the database is a good thing.