|
|
Archives of the TeradataForum
Message Posted: Wed, 30 Nov 2005 @ 23:54:03 GMT
Subj: | | Re: How to leave an intentional lock for testing |
|
From: | | Al MacGowan |
| From: McCall, Glenn David | |
That was a heck of a response.. It seems very simplistic to just CTRL-C the MLOAD process, but I guess it's a very valid point. I'll
definitely re-read your post in the morning when I'm fresh, and full of coffee.
The reason this has all come about is that we're structured with a QA dept, an ETL dept, and me, the lonely DBA. A while ago, we started some
standardization procedures, that included adding the TABLEWAIT into our MLOAD stages. Most of these changes were large enough to warrant full
testing of the ETL jobs by the QA dept. However, there was one job a few days ago that had only one change: add the TABLEWAIT option. So, what
does QA test to? Well, whatever's changed, of course. It doesn't help that there are always personal conflicts between QA folks and the ETL
folks. So, the end result is, QA says "tell me what's changed, and how i can validate your code is working appropriately". And VOILA - this
thread occurs, because who do they ask? The lonely DBA who's too busy fighting with Teradata's IDENTITY columns without enough knowledge of how
they work on Teradata.
Alistair MacGowan
Senior Database Administrator
| |