$$SWYNK$$ Featured Article(s) Learning MySQL with PHP – Making the Connection to MySQL This is a simple program to connect to mysql and extract information as easy as possible.how we can make a web page in PHP to connect to a MySQL database and show us the records on screen. Featured White Paper(s) Office 365 SharePoint Online – Architectural Considerations […]

Wrap Up Database Naming Conventions I thought I would close the thoughts on Database naming conventions with a few things I find helpful, and then include thoughts submitted by others. These are a few things I like to use in my naming conventions…these are ideas that I don’t simply follow blindly. I don’t mind long names for tables, views, columns, […]

Notice anything? swynk@sswug.org < Let me know what you think! Thoughts for Database Naming Conventions Today I have lots of food for thought when it comes to naming things in the Database. The meaning of data as well as the name of the data are frequent questions that have been asked. Some feel that meaning is more important than naming […]

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 […]

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 […]

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 […]

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 […]

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 […]

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 […]

Merge Comments Today I had a number of comments regarding an SQL merge process. Jason: If you do the update first you have X rows in the table that it has to evaluate to join on. Now when you delete you still have X rows to join on. I believe you said you do the insert after the update so […]