Author: Ben Taylor

Editorials

Database Object Naming Conventions

Database Object Naming Conventions Yesterday I tossed out the question regarding the relevance of naming conventions for hardware and software services. Today I’d like to share some insights others have shared regarding naming conventions for database objects as well. Jim writes: I think the answer lies with a couple of facets to “it depends”. It first depends on how big […]

Uncategorized

Are Naming Conventions Still Relevant?

Are Naming Conventions Still Relevant? I recall a discussion Steve introduced a couple years ago about naming conventions. In it we were discussing the value of how things were named that provided enterprise services. The discussion was targeted primarily at SQL Server. There was a lot of feedback with good ideas and good reasons behind them. Others simply used favorite […]

Editorials

Are Naming Conventions Still Relevant?

Are Naming Conventions Still Relevant? I recall a discussion Steve introduced a couple years ago about naming conventions. In it we were discussing the value of how things were named that provided enterprise services. The discussion was targeted primarily at SQL Server. There was a lot of feedback with good ideas and good reasons behind them. Others simply used favorite […]

Editorials

Editorial Thoughts for Today

Error Handling Final Comments Today I’m Wrapping up this series on error handling with some interesting insights from two of our readers. One is from an SQL Server perspective, and the other reflects code in all layers. Fraser Responds to Error Handling flow with the following thoughts: > Start at the highest level of code when handling errors. Personally I […]

Uncategorized

Error Handling ? When and Where

Error Handling – When and Where At the root of error handling is the need to identify the severity of the problem. If the problem is significant, then it is important to notify someone when the error occurred. These requirements determine the technique necessary to handle an error. When an error occurs in an application process initiated by an end […]

Editorials

Error Handling ? When and Where

Error Handling – When and Where At the root of error handling is the need to identify the severity of the problem. If the problem is significant, then it is important to notify someone when the error occurred. These requirements determine the technique necessary to handle an error. When an error occurs in an application process initiated by an end […]

Uncategorized

Database Error Handling

Database Error Handling SQL Server had a very simplistic error handling capability before SQL Server 2005 was released. The Global System Variable @@ERROR contained the value of any error occurring from the last statement. If no error it contained the value zero. For granular error trapping you had to test @@ERROR after each statement to assure all was well. SQL […]

Editorials

Database Error Handling

Database Error Handling SQL Server had a very simplistic error handling capability before SQL Server 2005 was released. The Global System Variable @@ERROR contained the value of any error occurring from the last statement. If no error it contained the value zero. For granular error trapping you had to test @@ERROR after each statement to assure all was well. SQL […]

Uncategorized

Error Handling Techniques

Error Handling Techniques In my opinion, Error handling is one of most important skills in enterprise level software. Often, handling errors is an afterthought, and is enhanced more often through need to debug code rather than a planned approach. I like to think of error handling with a few different dynamics. Managing the Proccess Flow Continue Processing Stop the process […]