Thank you. The next article (scheduled for publication on Nov 24th will deal pretty extensively with error handling. The third (submitted but no publish date yet) deals with Locks and Isolation levels.
I have to disagree with you about Oracle's superiority though. Having worked extensively with Oracle, I would say that there is very little advantage with its locking and transaction isolation support. It's true that in Oracle readers don't block writers and vise versa, but that locking strategy comes at a cost. Both SQL Server and DB2 use very similar locking strategies to great success. The key is to know the DBMS you use, understand its strengths and weaknesses and know how to get the most out of it.
Oracle's error handling is more consistent and easier to use, but from what I've seen, SQL Server 2005 will change that.
/*****************
If most people are not willing to see the difficulty, this is mainly because, consciously or unconsciously, they assume that it will be they who will settle these questions for the others, and because they are convinced of their own capacity to do this. -Friedrich August von Hayek
*****************/