Forum Replies Created

Viewing 15 posts - 46 through 60 (of 67 total)

  • RE: SQL & the JOIN Operator

    ryan.mcatee (10/7/2009)


    Speaking of queries, the ones in the article are simple examples, but when you're pulling many columns and joining on multiple keys, repeating full table names over and over...

  • RE: SQL & the JOIN Operator

    SuperDBA-207096 (10/7/2009)


    Wagner,

    You might want to mention in the:

    "Excluding the Intersection of the Sets" section this is similar to

    select... where not in (select... from table2) but it performs alot better...

  • RE: SQL & the JOIN Operator

    Jeff Moden (10/7/2009)


    Actually, they ARE becoming required. The use of table names instead of aliases has been deprecated.

    Even if they weren't, short table names may work fine but not...

  • RE: SQL & the JOIN Operator

    Andy DBA (10/7/2009)


    Yet another article that makes people think that table aliases (t1 and t2) are part of the required syntax. This first Join statement:

    SELECT t1.key1, t1.field1 as Name, t1.key2...

  • RE: SQL & the JOIN Operator

    Yet another article that makes people think that table aliases (t1 and t2) are part of the required syntax. This first Join statement:

    SELECT t1.key1, t1.field1 as Name, t1.key2 as...

  • RE: T-SQL Parsing Crazy Eights

    I know, formatting preferences are a whole can of worms. But I think "From Table1 Inner Join Table2" makes a lot of sense. I put the third table...

  • RE: T-SQL Parsing Crazy Eights

    SELECT

    StandingOrderLine.OrderNumber,

    StandingOrderLine.LineNumber,

    StandingOrderHeader.OrderTotal,

    StandingOrderPayment.PaymentAmount

    FROM dbo.StandingOrderLine INNER JOIN dbo.StandingOrderHeader

    ON StandingOrderLine.CompanyID = StandingOrderHeader.CompanyID

    AND StandingOrderLine.StandingOrderID...

  • RE: T-SQL Parsing Crazy Eights

    Tom Garth (9/30/2009)


    I agree with Tao that thoughtful aliasing, as opposed to A. B, C, will make code easier to read for the programmer, debugger, or DBA. Most who have...

  • RE: COPY_ONLY Backups

    I know that all of this is (supposedly) documented more fully in BOL, but the purpose of these articles is to help clarify the topics they write about. This...

  • RE: T-SQL Parsing Crazy Eights

    ssismaddy (9/23/2009)


    It might be the silly question....but, why we are not able to display e ??

    select 1.a -- gives the column name a and prints 1 ,...

  • RE: T-SQL Parsing Crazy Eights

    john.arnott (9/23/2009)


    David Walker-278941 (9/23/2009)


    Tao Klerks (9/23/2009)


    David Walker-278941 (9/23/2009)


    Yes, but I'm not forgiving of superfluous apostrophes in the word "its". The sentence gets a Fail. "It's" means "it is"...

  • RE: T-SQL Parsing Crazy Eights

    Tao Klerks (9/23/2009)


    David Walker-278941 (9/23/2009)


    Yes, but I'm not forgiving of superfluous apostrophes in the word "its". The sentence gets a Fail. "It's" means "it is" and nothing else.

    Ah...

  • RE: T-SQL Parsing Crazy Eights

    "The syntax parser is forgiving of missed spaces between a literal value and it's column alias."

    Yes, but I'm not forgiving of superfluous apostrophes in the word "its". The sentence...

  • RE: The T-SQL Paradigm

    Jeff Moden (4/6/2009)


    Aaron N. Cutshall (4/6/2009)


    David Walker (4/3/2009)


    Although this is off the original topic, I still haven't seen a SQL statement that was easier to read with the aliases than...

  • RE: The T-SQL Paradigm

    Timothy (4/3/2009)


    Are table aliases really that hard to decipher? Even if you had a query with 6 joined tables and every one of them using a single character table alias,...

Viewing 15 posts - 46 through 60 (of 67 total)