Comments on: SQL SERVER – Deferred Name Resolution

By: Irawan Soetomo

Irawan Soetomo — Thu, 25 Aug 2011 10:27:52 +0000

I want to commit suicide. I have a task to change the schema name of a db with over one thousand SPs. This ‘feature’ is killing me. I cannot be confident that my work is actually working. I wish there is a switch to prevent this.

By: pinaldave

pinaldave — Sat, 02 May 2009 04:28:27 +0000

@Tejinder Arora and @Hardeep Singh,

This applies to both tablename and column name. This is covered under different name resolution.

I will soon write down new post with explanation for the same.

Kind Regards,
Pinal

By: Hardeep Singh

Hardeep Singh — Fri, 18 Jul 2008 17:48:08 +0000

Hi Pinal,
I appreciate the way you have brought up this issue. But my curiosity still remains about why that happens. The issue is explained well in here but I think somehow the proper reason for this issue is missing.

I look forward to hear more on this from you.

Great Job Buddy!! Keep it up!!

Hardeep Singh.

By: Tejinder Arora

Tejinder Arora — Fri, 18 Jul 2008 17:02:00 +0000

I couldn’t get it either.Can you please explain it a bit more as if it is due to SQL Deferred Name Resolution it should behave same for both table names and Column names…Appreciate if you could provide some more explanation.
Regards
Tejinder

By: Jacob Sebastian

Jacob Sebastian — Thu, 17 Jul 2008 07:32:17 +0000

Great post Pinal.
Erland, SQL Server MVP has prepared a detailed paper which discusses the requirement for an option to strictly validate the TSQL code at compile time. He suggested SET STRICT_CHECK ON/OFF

http://www.sommarskog.se/strict_checks.html

He suggested an option like the “OPTION EXPLICIT” in visual basic. When this is turned on, SQL Server should perform a strict validation.

regards
Jacob

By: Red Bull

Red Bull — Tue, 15 Jul 2008 15:21:35 +0000

I am sorry i did not got it completely.

If the SQL does Deferred Name Resolution, then it should do for both table name and for columns name, why is it bias with the Column Name.