Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 

Content with tag naming standards Rss

   Items 1 to 20 of 29    Older >>
 

We'll go no more a' tibbling

Phil Factor points out the limitations and irritations of Hungarian Notation.  Read more...
By Phil Factor 2010/01/25 | Source: SQLServerCentral.com | Category: editorial
Rating: |  Discuss |   Briefcase | 393 reads

Enhancing the readability of your code: Table aliasing in sql

When writing SQL, picking good tables aliases can greatly enhance the readability of your code  Read more...
By Sylvia Moestl Vasilik 2009/05/07 | Source: SQLServerCentral.com | Category: sql server 2005
Rating: |  Discuss |   Briefcase | 7,824 reads

Best Practices for Database Design

One of the few things that SQL Server does not automatically help you with is the design of your tales, views, and other database objects. Having standards and design techniques can greatly ease the maintenance of your schema as well as ease the transition to having others work with the database. New author J.D. Gonzalez brings us some of his naming techniques to keep things organized.   Read more...
By J.D. Gonzalez 2008/06/20 (first published: 2005/04/06) | Source: SQLServerCentral.com | Category: naming standards
Rating: |  Discuss |   Briefcase | 50,011 reads

SQL Code Layout and Beautification

William Brewer takes a look at the whole topic of SQL Code layout and beautification, an important aspect to SQL programming style. He concludes that once you are tired of laying SQL out by hand, you had better choose a tool with plenty of knobs to twiddle, because nobody seems to agree on the best way of doing it.  Read more...
By Additional Articles 2008/05/26 | Source: SimpleTalk | Category: naming standards
Rating:  Rate this |   Briefcase | 5,369 reads

Practical Methods: Naming Conventions

Everyone should establish some sort of naming convention for their SQL Server platform. It helps to ensure that developers and DBAs can easily find objects and communicate with one another. New author Michael Lato brings us the start of a series on organizing your SQL Server code with an article on naming conventions.   Read more...
By Michael Lato 2007/03/07 | Source: SQLServerCentral.com | Category: naming standards
Rating: |  Discuss |   Briefcase | 13,787 reads

Practical Methods: Naming Conventions

Everyone should establish some sort of naming convention for their SQL Server platform. It helps to ensure that developers and DBAs can easily find objects and communicate with one another. New author Michael Lato brings us the start of a series on organizing your SQL Server code with an article on naming conventions.   Read more...
By Michael Lato 2007/03/07 | Source: SQLServerCentral.com | Category: naming standards
Rating: |  Discuss |   Briefcase | 13,787 reads

Best Practices for Database Design

One of the few things that SQL Server does not automatically help you with is the design of your tales, views, and other database objects. Having standards and design techniques can greatly ease the maintenance of your schema as well as ease the transition to having others work with the database. New author J.D. Gonzalez brings us some of his naming techniques to keep things organized.   Read more...
By J.D. Gonzalez 2008/06/20 (first published: 2005/04/06) | Source: SQLServerCentral.com | Category: naming standards
Rating: |  Discuss |   Briefcase | 50,011 reads

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.   Read more...
By Joseph Sack 2005/10/03 | Source: SQLServerCentral.com | Category: naming standards
Rating: |  Discuss |   Briefcase | 22,435 reads

Best Practices for Database Design

One of the few things that SQL Server does not automatically help you with is the design of your tales, views, and other database objects. Having standards and design techniques can greatly ease the maintenance of your schema as well as ease the transition to having others work with the database. New author J.D. Gonzalez brings us some of his naming techniques to keep things organized.   Read more...
By J.D. Gonzalez 2008/06/20 (first published: 2005/04/06) | Source: SQLServerCentral.com | Category: naming standards
Rating: |  Discuss |   Briefcase | 50,011 reads

Database Standards and Conventions

Having a good set of naming conventions for your SQL Server objects is one of the most vital things to a company. In the long duration of a business, it saves money and time as programmers are transferred internally and don't need to relearn object names. As learning curves lower, cost lowers. This article covers some of the conventions that Brian Knight uses and why he uses them.   Read more...
By Brian Knight 2005/02/25 (first published: 2001/05/29) | Source: SQLServerCentral.com | Category: naming standards
Rating: |  Discuss |   Briefcase | 27,712 reads

Coding Standards Part 2 - Formatting

The second part of Steve Jones' series on coding standards within SQL Server.   Read more...
By Steve Jones 2004/12/17 (first published: 2002/07/01) | Source: SQLServerCentral.com | Category: system development life cycle
Rating: |  Discuss |   Briefcase | 30,534 reads

Coding Standards - Part 1

A look at coding standards in SQL Server. The first part of this series deals with object naming standards.   Read more...
By Steve Jones 2004/12/10 (first published: 2002/05/09) | Source: SQLServerCentral.com | Category: naming standards
Rating: |  Discuss |   Briefcase | 47,207 reads

Worst Practices - Part 1 of a Very Long Series!

Andy starts a new series about Worst Practices - come find out why and read about the first one on his list - using Hungarian Notation for column names!   Read more...
By Andy Warren 2004/12/03 (first published: 2001/10/09) | Source: SQLServerCentral.com | Category: miscellaneous
Rating: |  Discuss |   Briefcase | 33,734 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!   Read more...
By Andy Warren 2004/11/12 (first published: 2002/09/12) | Source: SQLServerCentral.com | Category: system development life cycle
Rating: |  Discuss |   Briefcase | 37,552 reads

Standards Are a Good Thing

This week we have another article from Andy that discusses some changes he made at work in conjunction with clustering all his database servers. Not a how-to, just comments about what was changed and why. Worth reading just for the reminder about the potential gotcha that @@ServerName can represent.   Read more...
By Andy Warren 2003/04/09 | Source: SQLServerCentral.com | Category: administration
Rating: |  Discuss |   Briefcase | 6,148 reads

A Lookup Strategy Defined

Most databases designs nowadays seem to have at least a few if not many lookup or reference tables. This article helps you define a strategy in how to design, approve, and deploy them.   Read more...
By David Sumlin 2003/02/20 | Source: SQLServerCentral.com | Category: basics
Rating: |  Discuss |   Briefcase | 12,491 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!   Read more...
By Andy Warren 2003/02/14 | Source: SQLServerCentral.com | Category: administration
Rating: |  Discuss |   Briefcase | 8,336 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.   Read more...
By Andy Warren 2003/01/31 | Source: SQLServerCentral.com | Category: administration
Rating: |  Discuss |   Briefcase | 10,437 reads

Worst Practice - Bad Comments

This one is pretty interesting, Andy discusses a few things he sees in comments that not only fail to add value, they end up costing extra time. There's room for discussion here, but definitely a discussion worth having - comments can make you or break you, here's a chance to think about what you think is important in commenting and pass that on to your development team.   Read more...
By Andy Warren 2003/01/23 | Source: SQLServerCentral.com | Category: miscellaneous
Rating: |  Discuss |   Briefcase | 9,404 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!   Read more...
By Andy Warren 2004/11/12 (first published: 2002/09/12) | Source: SQLServerCentral.com | Category: system development life cycle
Rating: |  Discuss |   Briefcase | 37,552 reads
   Items 1 to 20 of 29    Older >>
 
Tags
strategies (15)    
database design (13)    
sql server 7 (6)    
administration (4)    
miscellaneous (4)    
programming (4)    
configuring (3)    
system development life cycle (3)    
t-sql (3)    
basics (2)    
best and worst practices (2)    
best practices (2)    
monitoring (2)    
coding standards (1)    
data types (1)    
editorial (1)    
performance tuning (1)    
sql server 2000 (1)    
sql server 2005 (1)    
sql-dmo (1)    
stored procedures (1)    
table aliases (1)    
visual basic 6 (1)    
worst practices (1)    
writing readable code (1)