Error message

Warning: Creating default object from empty value in _dxcontentbanner_set_details_blog() (line 206 of /appl1/devx/drupal/sites7/all/modules/devx/modules/dxcontentbanner/
Subscribe to Blog content and comments for carrie Latest blog posts

You’re in a time crunch. Maybe you’ve got an undersized backup environment that is incredibly slow, or you just have important stuff happening and you need to keep the software upgrade window as short as possible. You’ve been instructed to fully re-collect stats immediately after upgrading to Teradata 12 (T12), and you know there’s good stuff in the new T12 statistics, but, hey, life’s full of trade-offs. So what awaits you should you upgrade and just let your normal recollection routines refresh statistics over time?

Please note:  This content does not apply for sites on Teradata 13.10 or later releases.

Did you happen to catch my May 1, 2009, blog posting, titled ‘Utility Throttles – You Won’t Regret It’  I want to add an afterthought, a postscript, something I didn’t know about at the time I posted the blog. It concerns a characteristic of utility throttles that I can’t find documented anywhere, but that a co-worker alerted me to earlier this week.

If you’re thinking about using utility throttles, you might want to listen up.

Yeah, I know. All you need is another “thing to remember to do” following your upcoming hardware upgrade. As if your “must do” list wasn’t long enough already.

Well, consider what I’m giving you as a “soft” list…Its a few things worth checking after an upgrade, but the sky won’t fall in if you don’t get to it right way. So relax, take a deep breath, and ponder my post-expansion soft to-do list at your leisure.

I just got back from speaking at the San Francisco Teradata User Group meeting and my topic included techniques for controlling concurrency of load utilities. When I polled the audience, I was surprised and disappointed that so few in the audience were using utility throttles.

I’m a huge fan of utility throttles in Teradata, and I’d like to tell you why.

It’s taken me a while to warm up to the idea that rejecting queries can be good. I’ve always subscribed to the hippocratic oath of workload management: “Above all, do no harm to a query.” Yet lately I’m seeing more and more Teradata DBAs grimly, yet firmly, embracing filter rules as a new weapon in their arsenal. And they’re starting to like it.

Where is this lethal trend coming from?

NOTE:  This content is only relevant to sites on Teradata 12 or earlier.

Congratulations, you’re on Teradata 12! Now it’s time to start redefining your AMP worker task (AWT) monitoring procedures by making use of the new ResUsageSAWT table.