SQL Server Stored Proc Debate Continues... Will It Ever Stop?

You would say everything there is to know about Stored Procedures and whether or not they're the preferred way to go when it comes to database access, has been said already 3 years ago. In an extensive heated debate Rob Howard (pro) and Frans Bouma (contra) would have said all:

• Don't use stored procedures yet? Must be suffering from NIHS (Not Invented Here Syndrome)
  
• Stored procedures are bad, m'kay?

I clearly remember the debate, and lots of people referred back to these posts in the time between. Now however, Frans tells us a NEW debate is actually going on (A quote comes up: "Those who don't remember history are condemned to repeat is"

A very long thread (and when I say very I mean very!) over at TheServerSide.NETran a couple months ago, and is still getting contributions. On first side the arguments are still about the same as 3 years ago however, a bit mixed up and repeated... If you don't know about the old debate, it might be a good idea to read this one, just to get a feel for the different opinions out there on the subject. If nothing else, it will show you that even database access theory is not black & white.

For the rest I kindly refer you to Frans Frans's post for more info (otherwise I'm just going to click his one together, which wouldn't really add any value...

LINKBLOG for May 9, 2006

• VB.Net Tip: IIF is a function, not a language feature Leon Bambrick, the SecretGeek from down under, explains why you should NEVER use IIF to check for a divide-by-zero error. Take it to heart if the thought ever crossed your mind.
  


• A Snapshot View of .Net Deployment Mechanisms George Alexander always has something interesting to tell on the Visual Studio.NET platform. Now he's talking about the ways to deploy your VS.NET projects; basically it's choosing either (a) creating an installer package, (b) no-touch deployment, and (c) XCOPY deployment


• Interesting piece on translating websites for visitors from other countries. The author gives some tips you should keep in mind, e.g. should we do a translation at all (a professional translation is pricey), and should we choose localisation, which doesn't yield an exact translation, but rather a translation with the cultural context of the user in mind. It's worth a read --- unfortunately it's in Dutch (and it's too expensive for me to translate it in English :)
  Babelfish to the rescue. I was unable to find a way to link directly to the translated page unfortunately, so you have to cut and paste the link yourself, http://www.naarvoren.nl/artikel/vertalen. It's a rather cheep translation b.t.w., but hey nothing comes for free:
  

  A customer gives to a Internet site in several languages to want. Weet he where he to starts? Weet you where he to starts? With this Article in two parts I want give you a basis to remain the customer am able recommend and himself alert.