• Jason-299789 (1/8/2013)


    Id love to see the GenerateCalendar function.

    Coming from a DW background the persisted calendar table is second nature, and I'm surprised more traditional OLTP systems dont implement one as part of a standard build as its very low maintenance.

    At worst you might have to extend it and put in any regional public holiday's and business specific information (financial periods etc) as part of a once a year maintenance routine.

    PM'd you with the FUNCTION.

    I think most of the push back I get is because of a lack of understanding. I meant, by the way, here at work and not on the forums where Calendar tables are well established.

    I like to keep holidays in a separate table that can be joined on the Calendar table when needed. The Calendar table is then like, set it and forget it. Only the holidays table then needs maintenance annually. And can also then be country or state/province specific.


    My mantra: No loops! No CURSORs! No RBAR! Hoo-uh![/I]

    My thought question: Have you ever been told that your query runs too fast?

    My advice:
    INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
    The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.

    Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
    Since random numbers are too important to be left to chance, let's generate some![/url]
    Learn to understand recursive CTEs by example.[/url]
    [url url=http://www.sqlservercentral.com/articles/St