• We have a new client coming on line next year with a potentially, really high volume SQL 2008 database in which I anticipate many, many performance issues. I think there will be plenty of performance consulting and DBA opportunities for me there.

    I also plan to write a few more articles, although at this time I am a bit sketchy on the topics. I've had like 3 on the back burner for some time, so there is potential to get those up and running.

    I also have some SQL work planned for another client in Papua New Guinea that should prove interesting if small. Travel there is a real pain but it is quite likely that several trips there will materialize in the first 4 months of 2013.

    Certifications? Jeez, I'd love too but not even sure where to begin.

    Edit: Almost forgot. Plan to get TOAD up and running soon so I can start posting solutions that will work in either SQL Server or Oracle. Code portability don't 'cha know. That should keep Mr. CELKO happy!


    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