Forum Replies Created

Viewing 8 posts - 1 through 8 (of 8 total)

  • RE: Sins of SQL: The Time Table

    Lynn Pettis (6/3/2010)


    dan_public (6/3/2010)


    Lynn,

    OK. Now I'm confused too.

    Dan.

    That's okay, I just went through this thread and I can't find anywhere where I critisized any of your...

  • RE: Sins of SQL: The Time Table

    Lynn,

    OK. Now I'm confused too.

    Dan.

  • RE: Sins of SQL: The Time Table

    Lynn Pettis (6/3/2010)


    dan_public (6/3/2010)


    Lynn,

    Your point about constructive criticism is well taken. I'll keep that in mind and will scrub out the "crisp" language going forward. That said...

    I'm...

  • RE: Sins of SQL: The Time Table

    Lynn,

    Your point about constructive criticism is well taken. I'll keep that in mind and will scrub out the "crisp" language going forward. That said...

    I'm not sure why...

  • RE: Sins of SQL: The Time Table

    DeronDilger (6/2/2010)


    dan_public (6/2/2010)


    Steven,

    .....[G]oing forward, I will be on the lookout for your articles. And be sure not to read them.

    Have a nice day.

    Dan.

    Not having "29 years of...

  • RE: Sins of SQL: The Time Table

    Steven,

    The message that I'm (strongly) getting from you is that "My approach is best." As proof of "My approach is best", you keep bringing up the date range...

  • RE: Sins of SQL: The Time Table

    Besides the many issues raised about this approach, another issue not addressed by this approach is auditing. The Time dim (the most important dimension, IMO) is dynamic....

  • RE: SQL Function : Find ‘X’ Business Days in the Future

    A more effective solution would be to create a standard DateDim table. A well-indexed, robust DateDim table gives excellent performance and allows you easily define custom date rules...

Viewing 8 posts - 1 through 8 (of 8 total)