Click here to Skip to main content
15,908,909 members
Articles / Desktop Programming / Win32

T-SQL Coding Standard

Rate me:
Please Sign up or sign in to vote.
1.42/5 (15 votes)
1 Oct 2008CPOL 101.2K   2K   35   28
T-SQL Coding Standard - for programming the Microsoft SQL Server 2005 (DRAFT)

Introduction

I am currently working on a T-SQL coding standard to formalize our work. Having been inspired by the IDesign C# Coding Standard, I made this T-SQL Coding Standard Document. Maybe this will have some value for the community. It is work in progress and I intend to update it as my experience with its implementation continues.

Unfortunately, I wrote the document in Word using loads of formatting and CodeProject's editor cannot display the document directly. Instead, I leave the document here in a zip for download.

When the document has matured some more, I will reformat it in HTML and modify this article.

Casper Leon Nielsen - 21. Sep 2006. (modified 1st October 2008)

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


Written By
Architect HelloGroup
Denmark Denmark
Casper Leon Nielsen is a MCP/MCAD and is currently employed by HelloGroup a/s - a technical savy (yes that whats they are calling it these days) company.

Comments and Discussions

 
GeneralRe: Avoid using the blob type - NOT Pin
Casper Leon Nielsen21-Sep-06 23:53
Casper Leon Nielsen21-Sep-06 23:53 
Well there are pros and cons to both strategies. It is correct that using the database as a filestore can solve some issues and have some tantalising aspects:
Uniform access: Access to files can be encapsulated in the same type of datalayer components as the rest of the application.
Backup: Files will be backed up with the rest of the datastore.

But unfortunately it also tends to clog the visibility alot:
Users cannot interact with files through their normal tools, but have to extract them from the database to view and manipulate them.
Most components expects files to be excatly that: files in a directory structure and cannot interact directly with files in a datastore. This creates the need to unpack the files to a cache before using them.

So you are partly right: If you are the architect of a massive product, such as the before mentioned Sharepoint and MS CMS, you are well of trading visibility for structure. If however you are designing are solution on a smaller scale the tradeof is not as good.

To state however that "The notion of non using of blobs in db is outdated" is as valid as stating that "Designing an application using a multitiered approach is outdated, as Microsoft have now introduced DataAdapters that exist in the presentation layer" Laugh | :laugh: ...

I think I will rewrite the standard to simply state the tradeoffs instead of warning against the usage of blobs as file-storage.

Regards,
Casper

GeneralRe: Avoid using the blob type - NOT Pin
Casper Leon Nielsen22-Sep-06 0:38
Casper Leon Nielsen22-Sep-06 0:38 
GeneralRe: Avoid using the blob type - NOT Pin
__alias22-Sep-06 2:28
__alias22-Sep-06 2:28 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.