Archives of the TeradataForum
Message Posted: Wed, 05 Mar 2003 @ 23:50:31 GMT
<-- Anonymously Posted: Wednesday, March 05, 2003 18:13 -->
What good is having this information behind a firewall and not out where everybody can view it? Teradata customers aren't limited to the people who sign-up for committees or to people who have access to teradata@yourservice, but includes everybody who writes code for the teradata. My group works within our marketing department and although we write a lot of sql, we aren't considered techies and therefore our access to this kind of information is haphazard at best.
Our teradata dba, who works in another state, is the only one who has access and we can't get anything of value from him. Every time our group thinks it has a problem, we go to our dba. He drags his feet and eventually he opens an incident and contacts teradata. Teradata asks for information from the dba, he's busy so there is a delay before he passes the request back to us, we make it as simple as we can and he takes it back to teradata. Repeat this a couple of times and after a week or so, we find out it was a known problem. Speaking with other people at partners, it seems that this is more common than it should be.
I realize that the dba is our problem and we're working on it - but that doesn't get us any closer to having practical information about the teradata. How about doing something that makes it easier for the rest of us to do our job better? The better we do our job, the better teradata looks.
That should be repeated: The better we do our job, the better teradata looks.
As mentioned by others, use Microsoft Developer's Network and Knowledge Database as examples.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 28 Jun 2020|