Forum Replies Created

Viewing 15 posts - 2,341 through 2,355 (of 2,469 total)

  • RE: Error when using the IN Keyword on 100.000 elements

    Ron - at some point if someone decides to place the clustered index on another column then that's the one that will be "ordered by" IF THERE ARE NO OTHER...







    **ASCII stupid question, get a stupid ANSI !!!**

  • RE: Error when using the IN Keyword on 100.000 elements

    Alors...then can we move on to my original request for additional article/s on order/priority of clustered/nonclustered index scanning order?!

    Chris - I get the impression that you're in cahoots with Andy/Steve...







    **ASCII stupid question, get a stupid ANSI !!!**

  • RE: Error when using the IN Keyword on 100.000 elements

    (3 ligne(s) affectée(s))....

    No - you've never spoken it....just copied and pasted sometimes with french thrown in....

    & before you take this too seriously...I was only teasing when I said that!







    **ASCII stupid question, get a stupid ANSI !!!**

  • RE: Error when using the IN Keyword on 100.000 elements

    It's been a laborious and painstaking exercise but I spent all morning creating and testing a dummy table with 3 combinations of 2 columns - clustered and unique nonclustered; clustered...







    **ASCII stupid question, get a stupid ANSI !!!**

  • RE: Error when using the IN Keyword on 100.000 elements

    Joel - thanks for throwing that in - I certainly do not have more than a few thousand rows in all the tables I've tested so far...







    **ASCII stupid question, get a stupid ANSI !!!**

  • RE: Error when using the IN Keyword on 100.000 elements

    Yes - the second one was that defining primary keys do not necessarily mean a clustered index UNLESS (cutting & pasting from BOL to make life easier....):

    "IF a clustered index...







    **ASCII stupid question, get a stupid ANSI !!!**

  • RE: Error when using the IN Keyword on 100.000 elements

    Remi - I KNEW you would ask that & I should've addressed that first...

    No - I did not since I already had the setup to run queries...I can see what's...







    **ASCII stupid question, get a stupid ANSI !!!**

  • RE: Error when using the IN Keyword on 100.000 elements

    I have a table with an ID PK clustered index column...everytime I query it (regardless of whether my select includes the indexed column or any other combination of columns) I...







    **ASCII stupid question, get a stupid ANSI !!!**

  • RE: Error when using the IN Keyword on 100.000 elements

    No - to which one Frank ?







    **ASCII stupid question, get a stupid ANSI !!!**

  • RE: Date column Auto Convert on INSERT

    The filtering and validation should be done on the client side - can you not do this ? Splly. the dd & mm..







    **ASCII stupid question, get a stupid ANSI !!!**

  • RE: Error when using the IN Keyword on 100.000 elements

    Chris - doesn't a clustered index ensure that the rows are always returned in the order based on the indexed column ?!

    Also - a primary key doesn't implicitly mean...







    **ASCII stupid question, get a stupid ANSI !!!**

  • RE: Error when using the IN Keyword on 100.000 elements

    or you have a clustered index ?!?!







    **ASCII stupid question, get a stupid ANSI !!!**

  • RE: Select Query

    I tried this on one of our tables with about 7000 rows - running on a VERRRRRRY SLOW network - when the index wasn't clustered it took 22 seconds -...







    **ASCII stupid question, get a stupid ANSI !!!**

  • RE: Select Query

    Frank - make way for the next MVP







    **ASCII stupid question, get a stupid ANSI !!!**

  • RE: Select Query

    Remi - you're amazing!

    Haven't had time to compare execution plans yet (bet you already have) - but for sheer brevity and elegance your t-sql...







    **ASCII stupid question, get a stupid ANSI !!!**

Viewing 15 posts - 2,341 through 2,355 (of 2,469 total)