How many of you have come across a database that had stored procedures, views or functions and you had no clue, by name, what they were for? Having standard naming conventions helps to prevent that. Everyone has their own preferences and opinions on what they should be, so I thought I’d share mine. My opinion In a nutshell, the name of any object should be informative; specifically what the object is used for and where it is used. This is accomplished by utilizing prefixes in conjunction with specific naming conventions. I apply these standards to all of my stored procedures, views, and functions, whenever possible. Of course there are always…
-
-
For my first blog I want to talk about my experience as a member of SQL Family. My Start I started my career as a lone DBA, 15 years ago, with zero knowledge of what SQL Server actually was. I was promoted into a sole DBA job with expectations I would get certified and take the bull by the horns to manage the 50+ SQL Servers . The company, The Port of Virginia, took a big risk with me, but within 6 months’ time the gamble had paid off. In the beginning, most of what I learned to do the job was from a site called SSWUG.org. This is where…
