After timeouts we need to make sure that active transactions, if any, are rolled back. All timeout handling must be done on the client. This post provides the implementation and unit tests. Implementation The following class extends SqlCommand and rolls back active transactions after timeouts:     public static class ...

After the timeout, we may sometimes, but not always, end up with an outstanding transaction. If this is the case, we need to rollback the transaction ourselves. Otherwise the consequent commands which use the same connection might not work as expected. Let us debug through some client code and see what is happening in more ...

Transact-SQL is a great language for data manipulation, but it has its weaknesses. Unlike “real programming languages” T-SQL is confined to procedural code. Sure, you can build “modules” by using stored procedures and functions, but for the most part, all of the work will be procedural. It has in the past also lacked error handling syntax leaving ...

I've been fairly distracted this past week with my ''Bad habits to kick'' series, so apologies for being so late with the Connect digest.  I stumbled upon a few pretty interesting items from the past two weeks; I hope you find them interesting as well. #498082 : Allow direct usage of scalar functions in RAISERROR() It has bugged me that in ...