It is SQL NOT SBQL (Structured Business Query Language)(devlicio.us)

submitted by vistadbvistadb(879) 3 years, 2 months ago

Great rant on one of my favorite topics as well. SQL is not for all your business rules. :) Can I ask a stupid, rhetorical question? Why do we continue to put business logic inside of SQL Procs? Can anyone answer me this? About the only half way decent answer I have ever heard is: Because we have some of this type of logic (Business Logic/Rules) inside of a sql proc we are able to update/change/modify this rule on the fly without the need to redeploy assemblies. I am sorry, but this is about as lame of a reason to do something as I have ever read/heard. Yes, I will admit that when you do put logic into your procs you do not need to redeploy. However, you are making this decision at the expense of other, better decisions. When you put your logic inside your procs you are doing many, many things which I believe are bad.

add a comment |category: |Views: 1

tags: another

new Add a live kick counter to your blog >> liveImage

You can even customize the image by choosing your own colors, and then clicking the button below to update the preview and the html code:

  • "Kick It" text
  • "Kick It" background
  • kick count text
  • kick count background
  • border

Simply copy and paste this HTML into your blog post.


Users who kicked this story:
Comments:

No comments so far

information Login or create an account to comment on this story