Editorials

Smaller Procedures are Better Your Responses

SelectViews Show Available Now
Kalen Delaney on the show today talking about her work with SQL Server, upcoming workshops and other thoughts. Also on the show, SQL Server 2008 R2, Mary Leigh Mackey from AvePoint and much more.
[Watch the Show]

SSIS Class – Online, 12 Hours/classes
Eric Johnson’s class starts May 15 and you can register now to attend! Brought straight to your desktop, this 12-session class includes weekly business hours with Eric, LOTS of information about SSIS and how you can put it to use in your own shop. There is SO MUCH information packed into this course, it’s unbelievable. Take a look at the class sessions here.

If you’re working with SSIS, or considering it, you can’t go wrong.

[Find out more] here at the class site.

Smaller Procedures are Better – Your Responses

I expected to touch a nerve with this topic. Touching on the coding style used by developers can be sacred territory. However, I received a large number of responses from readers, all very much in agreement. I find it interesting that the primary reason stated for a more granular approach was not performance tuning. The primary goal was to have code that is easier to maintain and test. Without cherry picking, here are a number of your responses…

Aaron: I whole-heartedly agree with you, ever since embracing Unit Testing my stored procedures there is a conscience decision to only work w/ the data that I need and not include anything unless it’s required to pass the test. Not only have my SQL objects become more granular, but having the automated tests in the background has freed me from worrying about breaking something unintentionally.

Chris: Couldn’t agree more. I’ve been on that track for years and I’ve found it that it leads to higher quality and faster regression. My biggest challenge has been selling it. Some old school Database arch are just used to writing monolithic blocks and haven’t experienced the benefits of this approach.

Adym: Neat article, and right on the mark in my mind. Having written PL/SQL on Oracle and now Stored Procedures/Functions in SQL Server, I’ve always found that small code blocks are far easier to maintain than large blocks of code that do many tasks in sequence.

Kevin: The last few years I have been unit testing my stored procedures using both inline scripts and NUnit. Using Test First Development (TFD) or even Test Driven Development (TDD).

Agree? Disagree? Suggestions? Email me at btaylor@sswug.org.

Webcast: SharePoint Infrastructure: The databases, file structure, and services that make up your SharePoint Implementation.
In this session, we will discuss the various databases that are created when you install SharePoint from various options. We will also take a deeper look into the 12 hive file structure and the services that are required.
Presented by: Shannon Bray

> Register Now
> Live date: 5/12/2010 at 12:00 Pacific