Results 1 to 9 of 9

Thread: So You Wanna Be An SQL Server DBA...

Hybrid View

  1. #1
    A SQL Server fool GaryMazzone's Avatar
    Join Date
    Aug 2005
    Location
    Dover,NH
    Posts
    7,493

    Re: So You Wanna Be An SQL Server DBA...

    I use them but they really need to be thought about. Would you want to run the correlated query (which runs against every row) if you were pulling a record set with millions of rows? I would say this would be a problem.
    Sometimes the Programmer
    Sometimes the DBA

    Mazz1

  2. #2
    MS SQL Powerposter szlamany's Avatar
    Join Date
    Mar 2004
    Location
    Connecticut
    Posts
    18,263

    Re: So You Wanna Be An SQL Server DBA...

    I'm going to go out on a limb here and suggest that the correlated query - in an EXISTS() function - never returns any rows. It just makes it as far as the INDEX SEEK/SCAN or TABLE SCAN - finds that a row exists - and then it's job is done.

    *** Read the sticky in the DB forum about how to get your question answered quickly!! ***

    Please remember to rate posts! Rate any post you find helpful - even in old threads! Use the link to the left - "Rate this Post".

    Some Informative Links:
    [ SQL Rules to Live By ] [ Reserved SQL keywords ] [ When to use INDEX HINTS! ] [ Passing Multi-item Parameters to STORED PROCEDURES ]
    [ Solution to non-domain Windows Authentication ] [ Crazy things we do to shrink log files ] [ SQL 2005 Features ] [ Loading Pictures from DB ]

    MS MVP 2006, 2007, 2008

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width