chandrika5 (2/8/2013)
I am not sure how many people write new classic ASPs these days. Portability is the key here. I can deploy this SP in several SQL instances, and give developers access to this.: ASP or JSP or PHP etc. The SP is independent of web authoring server side language.
Good points but it will most likely depend on where the solution is needed. I gave classic ASP code because that was mentioned in your article. A similar function can easily be ported to .NET where it can be used by many languages. Having this simple function in the front-end means it will work with a variety of back-end databases (SQL Server, MySQL, Postgre, Oracle, ...) as well as all the .NET front-end languages.
Putting all the effort needed to make it work in an SP means it can work with a few other languages that are not .NET but will not work with any other databases.
So I guess either approach can be fine depending on the environment.
Enjoy!