Regular columnist Robert Marda had some extra time so we got him to take a look at the latest upgrade to SQL Compare - for those of you aren't familiar with it, it is a tool that will let you compare two databases to see the differences, then optionally sync one to the other.
This month Robert covers the process he uses for developing stored procedures. In many ways it reflects how software is developed, but it does have it's minor differences. This is a high level process discussion, not a line by line example of the entire process - by design of course.
Should your stored procedure continue when it hits an error? Or keep executing? What errors will cause a stored procedure to quit executing auotmatically? Regular columnist Robert Marda has at least some of the answers, we think you'll find this interesting.