cjsommer.com

, 2019-03-25

Rate

Share

Share

Rate

Related content

Stored Procedure Naming Conventions

As your SQL Server applications grow, chances are that you have more and more objects, especially stored procedures that you need to keep track of. An organized environment is key to being able to prevent the duplication of code and effort. Joe Sack brings us a look at how he names stored procedures to easy identification.

3.86 (7)

2005-10-03

22,547 reads

Managing Jobs - Part 2

Jobs are pretty basic aren't they? They are until you get a couple hundred, or a thousand. Andy continues talking about managing jobs by standardizing how you handle notifications and failures, and talks about an interesting idea to monitor jobs separately from SQL Agent. Worth reading!

2003-02-14

8,358 reads

Managing Jobs - Part 1

How many jobs do you have? 10? 100? 1000? Andy makes the point that what works to manage for a small number of jobs doesn't work when that number doubles or triples (well, unless you only had 1 job to start with!). In part one of two, this article looks at ideas for using categories and naming conventions to get things under control.

4 (1)

2003-01-31

10,457 reads

Worst Practices - Objects Not Owned by DBO

Last week Andy launched a new series about Worst Practices by talking about why the Hungarian naming convention is bad for column names. This week he's at it again, declaring that the practice of having objects owned by anyone other than dbo is BAD! Agree or disagree, we think you'll enjoy reading this article and adding your thoughts to the discussion!

4.86 (7)

2004-11-12 (first published: )

37,617 reads