Eirikur Eiriksson (1/29/2016)

---

Jeff Moden (1/29/2016)

---

GilaMonster (1/29/2016)

---

Jeff Moden (1/28/2016)

---

Rich Mechaber (1/5/2016)

---

You've probably got more material than you need by this point. This one's an old article, but I still find it useful to refer people to: https://www.simple-talk.com/sql/t-sql-programming/ten-common-sql-programming-mistakes/[/url].

It still amazes me that so many people with top ten lists still use single part naming conventions instead of 2 part naming.

Single-part naming for columns cost me most of this week. The replication problem I've been fighting with since Saturday turned out to be caused by a procedure with an ambiguous column error.

Heh... I feel for ya. I've not had a single problem in that area that cost me that much time but, every time I try to help some company with a particular problem, it's a nightmare anytime I have to fix a query on a system (even if I may be familiar with the system) because they don't use 2 part naming on the columns (or in the FROM clause, either). Especially in this day and age of Intellisense and similar tools, there's just no excuse to not do it and it saves a huge amount of time when troubleshooting. You already knew all that but had to say it out loud for anyone else following this thread.

I agree, it is amazing that one is constantly encountering this problem although I find it more common with developers which started developing on pre 2K5 versions of SQL Server.

😎