• (cs) in reply to bob
    bob:
    That is a really stupid thing to do........
    I think he was implying that.
    bob:
    Specifically because not all table data is suitable for 'indexing' ........ Hay lets just index these BLOBS & CLOBS Columns.
    I was thinking the same thing. What need would you ever have to index a description?
  • (cs) in reply to boog
    boog:
    I was thinking the same thing. What need would you ever have to index a description?
    Easy! You index a description if you want to find it quickly
  • (cs) in reply to The poop of DOOM
    The poop of DOOM:
    C-Octothorpe:
    Rawr:
    It's specifically pointed out that temp table is re-generated every query (of course it is) as if it's going to FUBAR the clustered index, which it won't.
    Who the fuck said it would FUBAR the index? There is no index to FUBAR, get it?
    Rawr:
    No one can say it's a WTF with the information that was given.
    Uh, yeah you can... Here: they put an index on a temp table rather than the source table. There ya go!
    Rawr:
    You assume they aren't using the temp table to query
    Not sure what you're trying to say here or where anybody would disagree with you...
    Rawr:
    I give them the benefit of the doubt
    Ah, there's your problem...
    That reads so nicely: "RAWR RAWR blablablabla RAWR RAWR blablablabla RAWR RAWR"
    Godammit! You sound like my wife... :)
  • Nagesh (unregistered)

    I am puting index card on detabase servers, but no preformance increase.

  • Obviously Obvious (unregistered) in reply to C-Octothorpe
    C-Octothorpe:
    The poop of DOOM:
    C-Octothorpe:
    Rawr:
    Barf Barf
    Blablabla
    That reads so nicely: "RAWR RAWR blablablabla RAWR RAWR blablablabla RAWR RAWR"
    Godammit! You sound like my wife... :)
    I have news for you: it is YOUR WIFE!
  • (cs) in reply to Obviously Obvious
    Obviously Obvious:
    C-Octothorpe:
    The poop of DOOM:
    C-Octothorpe:
    Rawr:
    Barf Barf
    Blablabla
    That reads so nicely: "RAWR RAWR blablablabla RAWR RAWR blablablabla RAWR RAWR"
    Godammit! You sound like my wife... :)
    I have news for you: it is YOUR WIFE!
    Yes honey, please come home! Our kids and I haven't seen you for three weeks already. Where did you go? You said you were just going out for a smoke...
  • Obviously Obvious (unregistered) in reply to The poop of DOOM
    The poop of DOOM:
    Obviously Obvious:
    C-Octothorpe:
    The poop of DOOM:
    C-Octothorpe:
    Rawr:
    Barf Barf
    Blablabla
    That reads so nicely: "RAWR RAWR blablablabla RAWR RAWR blablablabla RAWR RAWR"
    Godammit! You sound like my wife... :)
    I have news for you: it is YOUR WIFE!
    Yes honey, please come home! Our kids and I haven't seen you for three weeks already. Where did you go? You said you were just going out for a smoke...
    Last time we saw him, he was going all the way IN with the Zune
  • (cs) in reply to The poop of DOOM
    The poop of DOOM:
    Obviously Obvious:
    C-Octothorpe:
    The poop of DOOM:
    C-Octothorpe:
    Rawr:
    Barf Barf
    Blablabla
    That reads so nicely: "RAWR RAWR blablablabla RAWR RAWR blablablabla RAWR RAWR"
    Godammit! You sound like my wife... :)
    I have news for you: it is YOUR WIFE!
    Yes honey, please come home! Our kids and I haven't seen you for three weeks already. Where did you go? You said you were just going out for a smoke...
    I did; it was just a very long smoke... On an unrelated topic, I'll just be going out for a coffee now. BRB!

    Filed Under: deadbeat dad

  • (cs) in reply to C-Octothorpe
    C-Octothorpe:
    a very long smoke
    A pole smoke? (sorry too easy)
  • (cs) in reply to frits
    frits:
    C-Octothorpe:
    a very long smoke
    A pole smoke? (sorry too easy)
    What has zunesis done to you?
  • (cs) in reply to anonymouser
    anonymouser:
    Leenus:
    True WTF is saying indexes instead of indices
    you probably call multiple pointer input devices "mice" too, don't you?
    I call them "trackballs"...
  • (cs) in reply to C-Octothorpe
    C-Octothorpe:
    frits:
    C-Octothorpe:
    a very long smoke
    A pole smoke? (sorry too easy)
    What has zunesis done to you?
    Nothing *shivers*. The difference is that Zune would have added the "rape element" somewhere in there.
  • (cs) in reply to frits
    frits:
    C-Octothorpe:
    frits:
    C-Octothorpe:
    a very long smoke
    A pole smoke? (sorry too easy)
    What has zunesis done to you?
    Nothing *shivers*. The difference is that Zune would have added the "rape element" somewhere in there.
    Wind! Water! Fire! Earth! Heart! Rape!

    When these six elements combine, here comes... CAPTAIN PLANET!

  • (cs) in reply to The poop of DOOM
    The poop of DOOM:
    frits:
    C-Octothorpe:
    frits:
    C-Octothorpe:
    a very long smoke
    A pole smoke? (sorry too easy)
    What has zunesis done to you?
    Nothing *shivers*. The difference is that Zune would have added the "rape element" somewhere in there.
    Wind! Water! Fire! Earth! Heart! Rape!

    When these six elements combine, here comes... CAPTAIN PLANET!

    HA! Yeah, zune would be "Rape" in a gimp outfit.

  • Joe Blow (unregistered)

    I am a software developer and I have a pickup truck....it's a double whammy.

  • (cs)

    I just decided I don't like the term "enterprisey" for cases like this. I think we ought to switch "enterpriseismic" (EN-ter-pry-SIGHS-mic)...

    ...as in earthquake...

    ...as in disaster.

  • Rat (unregistered) in reply to Steve The Cynic
    Steve The Cynic:
    anonymouser:
    Leenus:
    True WTF is saying indexes instead of indices
    you probably call multiple pointer input devices "mice" too, don't you?
    I call them "trackballs"...
    Is that just the males?
  • Grefg (unregistered) in reply to Coyne
    Coyne:
    I just decided I don't like the term "enterprisey" for cases like this. I think we ought to switch "enterpriseismic" (EN-ter-pry-SIGHS-mic)...

    ...as in earthquake...

    ...as in disaster.

    Why not just enterpreismic?

  • Geoff (unregistered) in reply to bob

    "Unless the reporting is doing some sort of joining/ selects against other tables with the temp data, which would be another WTF. "

    I am not sure that is always a WTF. Frequently data gets organized into Parent-child relationships which may simply inserts of new records (where the parent ID) will be know by the software doing the insert. Lowing the cost of inserts transaction may be very important, but make reporting a pain. That can be a good trade.

    Often in those cases you will produce a "flattened" temp table to report against, that might indeed join with other things.

  • The Holey Order of the Zune (unregistered) in reply to C-Octothorpe
    C-Octothorpe:
    The poop of DOOM:
    frits:
    C-Octothorpe:
    frits:
    C-Octothorpe:
    a very long smoke
    A pole smoke? (sorry too easy)
    What has zunesis done to you?
    Nothing *shivers*. The difference is that Zune would have added the "rape element" somewhere in there.
    Wind! Water! Fire! Earth! Heart! Rape!

    When these six elements combine, here comes... CAPTAIN PLANET!

    HA! Yeah, zune would be "Rape" in a gimp outfit.
    [image]

  • barf4eva (unregistered) in reply to boog

    It's disturbing that you think this is true of DBAs.. You must have had some bad experiences. I don't think, however, that your experiences are indicitive of general knowledge of a DBA. At least where I work, they know quite a bit about indexing.

  • (cs) in reply to barf4eva
    barf4eva:
    It's disturbing that you think this is true of DBAs.. You must have had some bad experiences. I don't think, however, that your experiences are indicitive of general knowledge of a DBA. At least where I work, they know quite a bit about indexing.
    I certainly don't think this is true of all DBAs, or even most DBAs, and I certainly wasn't implying that my experiences are indicative of any DBA's general knowledge. I've actually worked with a lot of very smart DBAs.

    But yes, I have had some bad experiences. I have worked with data warehouses (large tables, updated nightly) that had poor indexing (bad column order, for example) on some tables and no indexing on others. I've worked with databases that had no primary keys, foreign keys, etc. I have even worked with DBAs that have literally told me "I don't know much about indexes," in those exact words. I'm surprised and disturbed at how many I've encountered.

  • SQLMaster (unregistered) in reply to anonymouser
    anonymouser:
    Leenus:
    True WTF is saying indexes instead of indices
    you probably call multiple pointer input devices "mice" too, don't you?

    Nah, that sounds too dicey...

  • Bob (unregistered) in reply to Ken Row
    The WTF is that, at least on some DB products, building a clustered index means the entire table gets physically re-arranged so that its data matches the order of the index.

    Ummmmmmmmmm, that's the point. Otherwise it's just a regular index. That's why you get exactly one clustered index per table, and why if you're selecting by the clustered index's field(s), it's as fast as it can possibly be.

  • Bob (unregistered) in reply to Brian White
    Sure it can make sense. Are you going to join to that table a lot on the id? It also allows the fastest writes, since the new row always goes at the end, instead of needing to reshuffle the (potentially huge) table to fit it in somewhere in the middle. You can also be sure that that particular column will never ever change, whereas pretty much any other column in the table could change, triggering a re-shuffling of the row in addition to updating the column. There are some high level DBA articles I've seen that argue that clustering on anything other than an identity column will eventually cause problems.

    Joo need to go back to DBA school, mang. A clustered index on an incremental field is just about the worst choice for a clustered index. You WANT to vary the insertion point so that you don't hot spot the leaf nodes. That's where the fill-factor comes in, with regard to re-ordering the physical pages. Actual usage and testing are required to figure out the optimal set up, but decent guessing based on expected transaction throughput and size can work.

    Those articles you mention are no doubt written by people with absolutely no understanding of a b-tree.

    The advice quoted is so unbelievably bad, it HAS to be sarcastic.

Leave a comment on “The Temporary Index”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article