 |
 |
Archives of the TeradataForum
Message Posted: Mon, 11 Mar 2003 @ 02:13:02 GMT
| Subj: | | Re: Teradata Production, Acceptance Test, Testing and Development environments |
| |
| From: | | Sid Gudes |
Jim Downey wrote:
| | We have had the fortune of having two large Teradata platforms available for Testing and Production. Certainly this is not the case
in every Teradata shop. How do other organizations handle the need to have separate environments for the following: | |
| | 1. Production.
2. Acceptance Testing.
3. Testing.
4. Development. | |
| | This would include projects required to load new data or make changes to existing sources, build summary tables, build new
reports and reporting applications. Build new extracts etc... | |
| | Presumably you want a production environment that is separate from the testing and development environments. Does anyone use their
production environment for testing or development? | |
| | I would appreciate any thoughts on strategies that have worked or some that haven't worked. | |
For development, we install Teradata for Windows on each developer's local PC (we use Win 2000). This way developers can just take
their laptop with them and do development independently. Installing Teradata under Windows doesn't take very long, and data can be quickly
loaded and backed up via arcmain.
We then have a small shared server for testing (also Windows). Our customers do acceptance testing and production, and always (so far)
have had separate (Worldmark) hardware for these.
Regards,
Sid Gudes
PIA Systems Corporation
| |
