Outer Joins
-
and now after re-reading it it does in fact mention a version,
my bad :blush:
---------------------------------------------------------------------------------------
The more you know, the more you know that you dont know -
ShaynThomas1983 (12/18/2015)
At no point does the question mention a SQL version....unless i missed something, or are we to assume all questions are using the latest version(s)?,Ta:Whistling:
Unless the question specifies otherwise, always assume it is for the latest production version of SQL Server.
-
Xavon (12/18/2015)
I'm new enough to SQL server I did not even know this syntax. I thought it might be a typo, but I looked it up just in case. I was ready to give the right wrong answer (treat it as a LOJ) until I saw 2014 specified in the question. At that point I realized it must have been removed, and selected error, and got it right.Good for you for not knowing that syntax and don't take the time to learn it!
Alvin Ramard
Memphis PASS Chapter[/url]All my SSC forum answers come with a money back guarantee. If you didn't like the answer then I'll gladly refund what you paid for it.For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
-
Despite it's occasional problems (mostly caused by humans), I loved the old syntax... it was great for job security especially since we also used Oracle and it's exactly the opposite.
--Jeff Moden
RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.Change is inevitable... Change for the better is not.
Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally) -
Jeff Moden (12/18/2015)
Despite it's occasional problems (mostly caused by humans), I loved the old syntax... it was great for job security especially since we also used Oracle and it's exactly the opposite.I can't remember it in Oracle - but then the last time I had anything to do with Oracle was in 1995 and and the last time I wrote any Oracle SQL (PL-SQL?) was a few years before that.
Tom
-
helenlu7 65408 (12/17/2015)
*= or=*
Have been depricated since SQL 2005? long time ago ....
They were part of MS dialect of T-SQL, not compliant with Standard, so they had to go
*= and =* are working only with database having a compatibility level set to 80 ( corresponding to SQL Server 2005 ). Not supported by SQL Server 2014 , I am not sure for 2008 R2 ( 10.5 ) but supported in SQL Server 2008.
but , a question about which I have no answer : the percentage of databases running on SQL Server 2008 in comparison of the whole SQL Server databases ? I may go wrong , but I don't think that there is an available support from Microsoft for 2008 .For SQL Server 2008 R2 , I think that the end of life time is approaching.
I have been able to find the "good answer" because I have followed a thread in the MSDN forums ( about T-SQL ) after the launch of SQL Server 2008/2008 R2.
Have a nice day.
-
I always use explicit words for my joins.
-
patricklambin (12/20/2015)
I may go wrong , but I don't think that there is an available support from Microsoft for 2008 .For SQL Server 2008 R2 , I think that the end of life time is approaching.Oddly enough, that means that it'll finally be "stable".
--Jeff Moden
RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.Change is inevitable... Change for the better is not.
Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)
Viewing 8 posts - 16 through 22 (of 22 total)
You must be logged in to reply to this topic. Login to reply