Comments on: SQL SERVER – Guidelines and Coding Standards Part – 1

By: deepak

deepak — Tue, 13 Dec 2011 11:53:42 +0000

hi ,
this is Deepak,i want to know can we write two queries in single query i.e. counting number of rows and selecting total rows and putting that query in resultset is it possible?
thanks in advance

By: pinaldave

pinaldave — Tue, 06 Dec 2011 16:35:09 +0000

Thanks to Aaron Bertrand for their feedback in correcting few of the incorrect information. I request you to read his excellent article here – http://sqlblog.com/blogs/aaron_bertrand/archive/2008/10/30/my-stored-procedure-best-practices-checklist.aspx for Best Practices Checklist.

By: Sateesh Kumar P

Sateesh Kumar P — Wed, 28 Sep 2011 08:16:41 +0000

Great Post!!!

By: Praveen

Praveen — Mon, 18 Jul 2011 08:40:11 +0000

nice post

By: ssingh

ssingh — Sun, 05 Sep 2010 11:55:57 +0000

Nice article.

Thanks a Lot…

By: vanitha

vanitha — Wed, 25 Aug 2010 06:41:22 +0000

Hi Dave,

Very interesting to see your blog.I m a beginner of Sql Server.when i search queries in Google, your blog will come in the top.most probably i ll prefer your blog to learn.So keep share your knowledge with all and i proud to say u r my role model for my sql knowledge..

thanks a lot

By: Sumit

Sumit — Tue, 15 Jun 2010 04:25:48 +0000

very nice article…….

By: Zehng

Zehng — Sat, 27 Mar 2010 19:24:21 +0000

Pinal,

Great tips. Thanks for sharing.

Regards,
Zehng

By: Madhivanan

Madhivanan — Mon, 08 Mar 2010 10:43:14 +0000

There is no actual advantage. It depends on the person who names them

By: Devaraj Diraviyam

Devaraj Diraviyam — Tue, 15 Dec 2009 11:16:37 +0000

Hi Pinal,

Is there any advantage of using ‘s’ at the end of the Table or View?

A great post

Devaraj Diraviyam
System Architect

By: Pol28

Pol28 — Thu, 22 Oct 2009 19:27:05 +0000

With the current there is a rise in the number of facilities and a decrease in funding and staffing in the Air Inspections Program. ,

By: Bharat Shah

Bharat Shah — Sat, 10 Oct 2009 12:24:28 +0000

hello sir,

Can u send me the complete reference of ‘CREATE INDEX’ which session was taken by u on 3rd october.

You have announced that, if anybody will send me request me
i will send the comepete reference of ‘CREATE INDEX’ with Examples.

By: Bill Gibbs

Bill Gibbs — Thu, 30 Jul 2009 13:54:51 +0000

sorry for late response, but this is an interesting thread. as for prefixes, they are used in most environments and help to keep things consistent, because when you are calling sp from application code, the prefix really helps…and for user sp, usp_ does the trick. also, yay Schemas! having to work on DBs where 1000s of tables are dumped together, and you have to figure out how they relate and what the logical groupings are, Shemas are a great underused way to manage this.

By: Alex Romanov

Alex Romanov — Thu, 11 Jun 2009 14:30:25 +0000

Microsoft does not reccomend using sp prefix for stored procedures because it is alreday used by system stored procs and user defined proc with sp in it will have additional overhead during name complie process

By: Brian Tkatch

Brian Tkatch — Mon, 09 Mar 2009 14:01:47 +0000

The SET NOCOUNT link should probably point o http://blog.sqlauthority.com/2007/04/28/sql-server-good-better-and-best-programming-techniques/comment-page-1/ where he says: “Remember to SET NOCOUNT ON at the beginning of your SQL bataches, stored procedures, triggers to avoid network traffic. This will also reduct the chances of error on linked server.”

By: Brian Tkatch

Brian Tkatch — Mon, 09 Mar 2009 13:53:16 +0000

“The table is Customers (with the s, becuase that is what is in the table as a whole, the customers)”

That is not how i see it at all. The TABLE merely defines the records within it, which each are, individually, one customer.

By: Michael

Michael — Fri, 06 Mar 2009 22:34:32 +0000

I think that by adding sp to a stored procedure the sql engine looks first in the master db for the stored procedure.

I do not like any prefixes – name stored procedures based on the table/object they most affect and what they do based on CRUD

CustomerGet (get one customer)
CustomerSelect (get more than one customer)
CustomerUpdate
CustomerAdd
CustomerDelete

The table is Customers (with the s, becuase that is what is in the table as a whole, the customers)

a view that joins between Customers and Accounts and groups on customer (where a customer can have more than one account). Since Customer is the group by it is listed first in the name

CustomersAccounts

Accounts and Customers listed by account, since account is the group by it is listed first in the name

AccountsCustomers

By: mi mi

mi mi — Fri, 03 Oct 2008 18:20:26 +0000

just to bring it to your attention that “Read More” link regarding SET NOCOUNT ON is pointing to “SQL SERVER – Simple Cursor to Select Tables in Database with Static Prefix and Date Created” page.

By: Sinix

Sinix — Wed, 01 Oct 2008 00:58:05 +0000

> If you have big subset of table group than it makes sense to give prefix for this table group. Prefix should be separated by _.

> Use following naming convention for Stored Procedure. sp_[_] Where action is: Get, Delete, Update, Write, Archive, Insert… i.e. verb

Use SCHEMAs, Luke :)

I’d like to see good old approach “fit all that info in that damn short name”. But I’ll not be happy if I find it in our projects. Precisely, I will be very, very unhappy :)

We prefer to spread our projects on several databases (the separation is based on domain scopes) and schemas (there are no strong rules, but we prefer to create separate schemas for each API segment).

Good luck, guys! Be happy:)

By: SQL SERVER - Guidelines and Coding Standards Complete List Download Journey to SQL Authority with Pinal Dave

Thu, 25 Sep 2008 10:34:31 +0000

[...] SQL SERVER – Guidelines and Coding Standards Part – 1 [...]

By: Kamran Shahid

Kamran Shahid — Wed, 24 Sep 2008 07:39:16 +0000

Another nice post.

What About composite Primary Key

[
* Primary Key : PK_

Example:

PK_UserDetails

PK_ Emails
]
??

By: Gadi

Gadi — Tue, 23 Sep 2008 19:11:52 +0000

I find that when coding SQL queries with multiple joins that this format is more readable.

SELECT Username, Password
FROM UserDetails ud INNER JOIN
Employee e ON e.EmpID = ud.UserID

This was I can easily see which tables are included in the query.

By: pinaldave

pinaldave — Tue, 23 Sep 2008 16:02:37 +0000

Speednet,

Your suggestions are valuable.

Kind Regards,
Pinal

By: Speednet

Speednet — Tue, 23 Sep 2008 15:57:51 +0000

I’m such a dope, I called you by your last name, sorry Pinal.

By: pinaldave

pinaldave — Tue, 23 Sep 2008 15:00:46 +0000

Speednet,

I appreciate your feedback. I will follow up on it.

Kind Regards,
Pinal