Lon-860191 (11/8/2010)

---

Only one small comment, the answer depends on collation for the database where the commands are issued. Some collations are case-sensitive so only the create statement would work and the rest would fail because the table doesn't exist. Other than that absolutely perfect.

Lon

SanjayAttray (11/8/2010)

---

^{Create Table #Test (a int, b int, C as a+b )
go
insert into #test values (3,4)
insert into #test values (1,7)
go
select * from #test
order by 1
go
drop table #test
go}



Isn't it funny that when you say order by 1, sql server assumes 1 as column and gives result order by column 1 but at the same time when you execute

select 1 from #test

you get result as 1

Create Table #Test (a int, b int, C as a+b ) 
go
insert into #test values (3,4)
insert into #test values (1,7)
go
select 1 from #test

go
drop table #test

(1 row(s) affected)

(1 row(s) affected)

-----------
1
1

(2 row(s) affected)

john.arnott (11/8/2010)

---

Hmmm. When I run this code to build the table, "Select 1 from #test" returns two rows, each with a "1". It's an implied join, isn't it?

Create Table #Test (a int, b int, C as a+b ) 
go
insert into #test values (3,4)
insert into #test values (1,7)
go
select 1 from #test

go
drop table #test

UMG Developer (11/8/2010)

---

Nice question, I would have gotten it wrong had the option for the problem with + not been there. (I didn't see the computed column so once I went looking for the + I immediately knew what was going to happen.

Thanks!

RichardDouglas (11/9/2010)

---

I thought the title gave it away

Hugo Kornelis (11/9/2010)

---

Nope, no join at all. . . . .

...when you execute

select 1 from #test

you get result as 1