• Alan.B (1/8/2013)


    Great article Dwain! It also inspired me to read the N-Tuple article which I liked.

    It’s almost a shame (not really! J) that I no longer support Accounting applications because these scripts would undoubtedly save me countless hours of manual reconciliation.

    I supported accounting applications and could have used these (my first SQL job was supporting an accounting app that ran on NT4, SQL 6.5). I could have also used this then or during the parts of my college classes where I where we had to figure out why the books did not balance.

    Edit: Didn't run out of stuff to say... accidently hit enter and posted incomplete comment...

    Glad you liked it Alan. I think it may be difficult for some people that haven't supported bean counters to understand how inane and time consuming some of their problems are. πŸ˜›

    My first article Financial Rounding of Allocations[/url] is another example drawn from that experience.

    Thanks for stopping by.


    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