Archives of the TeradataForum
Message Posted: Tue, 20 Jun 2000 @ 15:06:21 GMT
This actually raises a good point. A significant portion of our members are consultants who don't have direct access to NCR resources. After all, many of us are in competition with NCR Professional Services.
One of the things that I had hoped when starting TDATA-L was that there would be a sharing of problems. We have all been there: you get hit by a show-stopping problem and report it to NCR's GSC. After sending SQL, DDL, crashdumps ("can't be read, send another"), several weeks past and then after being told that the problem can't be duplicated, you find out that somebody previously had the problem and a fix was available all along.
I'm hoping that we can share our problems so that we don't have to discover and analyze the problems one-by-one, but rather that we can collectively have an awareness of the known problems (without waiting until the CEO or the CFO asks on Monday morning why the weekly report is wrong - again).
Please don't take this as a criticism of the GSC: Even though problems frequently sound similar, they can have different causes and the GSC is trying to find the best answer for us. It's a tough job. At the same time, I think that we would be in a better position if we were aware of problems in advance. That way, we can spend our time being proactive rather than reactive. Our job is tough too.
I like the idea of posting problems to TDATA-L, but keep in mind that there are some of us who have no access to NCR internal documents. So letting us know that there is a problem can be really helpful, providing a DR number (and similar references) is even more helpful and giving some idea of what is in the DR is even better still. Best of all, is to learn that a problem has been fixed.
Just a word of caution, it's best to assume NCR's documentation is not for public dissemination and anything sent to the TDATA-L Discussion Group should be considered as being in the public domain. Some of the information that you may receive from NCR could be covered by a Non-Disclosure Agreement. So please don't send internal NCR documents to the TDATA-L list and be careful in what you do send. Other than those cautions, this is the best place for us to exchange Teradata knowledge and experiences. Rumors and gossip are always welcomed.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 28 Jun 2020|