Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Saturday, November 2, 2013 8:22 AM
Declare @ExportDate datetime='2013-10-23'
Declare @Code nchar(2)=47
Declare @AreaNumber nvarchar(4)=2301
select SUBSTRING(ExportEntityNumber,3,2) as DepartmentCode,COUNT(*)
from Rel_Entity_Indicator
where
ETC=565 and
SUBSTRING(ExportEntityNumber,len(ExportEntityNumber)-3,4)='2301' and
ExportDate>@ExportDate
group by DepartmentCode
and we have this error message:
Msg 207, Level 16, State 1, Line 11
Invalid column name 'DepartmentCode'.
why this happen?
Saturday, November 2, 2013 8:40 AM ✅Answered
Its because Group By is processed before the select clause ,
The logical processing order of a query in SQL Server http://letuslookintosqlserver.blogspot.in/2013/08/logical-query-execution-in-sql-server.html
try,
select DepartmentCode,COUNT(*) from(
select SUBSTRING(ExportEntityNumber,3,2) as DepartmentCode,*
from Rel_Entity_Indicator
where
ETC=565 and
SUBSTRING(ExportEntityNumber,len(ExportEntityNumber)-3,4)='2301' and
ExportDate>@ExportDate) A
group by DepartmentCode
Please use Marked as Answer if my post solved your problem and use Vote As Helpful if a post was useful.
Saturday, November 2, 2013 10:00 AM ✅Answered
Hi,
You can also try like this ,
Declare @ExportDate datetime='2013-10-23'
Declare @Code nchar(2)=47
Declare @AreaNumber nvarchar(4)=2301
select SUBSTRING(ExportEntityNumber,3,2) as DepartmentCode,COUNT(*)
from Rel_Entity_Indicator
where
ETC=565 and
SUBSTRING(ExportEntityNumber,len(ExportEntityNumber)-3,4)='2301' and
ExportDate>@ExportDate
group by SUBSTRING(ExportEntityNumber,3,2)
As said by Sarat , it is because of logical query processing order , you can use alias name of column in the SELECT statement for ORDER BY clause not for GROUP BY clause .
Related reference links :
http://blog.sqlauthority.com/tag/logical-query-processing-phases/
sathya - www.allaboutmssql.com ** Mark as answered if my post solved your problem and Vote as helpful if my post was useful **.
Sunday, November 3, 2013 11:06 PM
Here is how a SELECT works in SQL ... at least in theory. Real products will optimize things, but the code has to produce the same results. All of your postings tell us that you have never read a book on SQL and have no idea what the basics of the language. Asking question in a Forum is not how to learn!
a) Effectively materialize the CTEs in the optional WITH clause. CTE's come into existence in the order they are declared so only backward references are alllowed. A CTE can be recursive. Think of them as VIEWs that exist only in the scope of the query. In practice, if they are used once then they are implemented as an in-line macro.
b) Start in the FROM clause and build a working table from all of the joins, unions, intersections, and whatever other table constructors are there. The <table expression> AS <correlation name> option allows you give a name to this working table which you then have to use for the rest of the containing query. Ther are UNION, INTERSECT and EXCEPT set constructors, LATERAL tables, table-valued function and all kinds of things happening in here.
c) Go to the WHERE clause and remove rows that do not pass criteria; that is, that do not test to TRUE (i.e. reject UNKNOWN and FALSE). The WHERE clause is applied to the working set in the FROM clause.
d) Go to the optional GROUP BY clause, partiton the original table into groups and reduce each grouping to a *single* row, replacing the original working table with the new grouped table. The rows of a grouped table must be only group characteristics: (1) a grouping column (2) a statistic about the group (i.e. aggregate functions) (3) a function or constant(4) an expression made up of only those three items. The original table no longer exists and you cannot reference anything in it (this was an error in early Sybase products).
e) Go to the optional HAVING clause and apply it against the grouped working table; if there was no GROUP BY clause, treat the entire table as one group.
f) Go to the SELECT clause and construct the expressions in the list. This means that the scalar subqueries, function calls and expressions in the SELECT are done after all the other clauses are done. The AS operator can also give names to expressions in the SELECT list. These new names come into existence all at once, but after the WHERE clause, GROUP BY clause and HAVING clause have been executed; you cannot use them in the SELECT list or the WHERE clause for that reason.
If there is a SELECT DISTINCT, then redundant duplicate rows are removed. For purposes of defining a duplicate row, NULLs are treated as matching (just like in the GROUP BY).
g) Nested query expressions follow the usual scoping rules you would expect from a block structured language like C, Pascal, Algol, etc. Namely, the innermost queries can reference columns and tables in the queries in which they are contained.
h) The ORDER BY clause is part of a cursor, not a query. The result set is passed to the cursor, which can only see the names in the SELECT clause list, and the sorting is done there. The ORDER BY clause cannot have expression in it, or references to other columns because the result set has been converted into a sequential file structure and that is what is being sorted.
As you can see, things happen "all at once" in SQL, not "from left to right" as they would in a sequential file/procedural language model. In those languages, these two statements produce different results:
READ (a, b, c) FROM File_X;
READ (c, a, b) FROM File_X;
while these two statements return the same data:
SELECT a, b, c FROM Table_X;
SELECT c, a, b FROM Table_X;
Think about what a confused mess this statement is in the SQL model.
SELECT f(c2) AS c1, f(c1) AS c2 FROM Foobar;
That is why such nonsense is illegal syntax.
--CELKO-- Books in Celko Series for Morgan-Kaufmann Publishing: Analytics and OLAP in SQL / Data and Databases: Concepts in Practice Data / Measurements and Standards in SQL SQL for Smarties / SQL Programming Style / SQL Puzzles and Answers / Thinking in Sets / Trees and Hierarchies in SQL