Submitting New Database
Overview
The Teradata University Network accesses a Teradata database server for use by
professors who teach database and data warehouse courses. A description of the
available course databases is available at
http://tunweb.teradata.ws/tunweb/databases.html. Professors can add new databases
to the Teradata server by following the process described below. The new database will
be available for all professors and students to use with any course. All databases are
read only.
Process
To add a new database to Teradata University Network, you must own the database or
have permission from owner of the database.
1. First, send the database description, database content, and approximate
database size to Stan Ozenbaugh (stan.ozenbaugh@teradata.com). The
following sections contain details on the items that you need to send.
2. After the database is approved, your materials are forwarded to the Teradata
University Network development team.
3. Once your database is approved, it will be loaded to Teradata University
Network. You will be notified when your database is available.
Format – File Size
The maximum size of an email attachment to Teradata is 5MB. Therefore, the database
items should be zipped into one or more files that are each less than 5MB and then sent
via email. If the items are too large to easily produce small zip files, then large zip files
can be made available via an FTP server or a Web server. Then you only need to send
the URL for the zip files.
Format – Database Description
You must supply a description for your database that is similar to the other database
descriptions on the site. If the database is used with a textbook, then descriptions of the
tables can be referenced in the textbook. If a textbook is not available, then you should
send the table descriptions as a text file, Microsoft Word document, or Adobe pdf
document. You must also include your name and email address with the database
description. You may recommend a Teradata database name; however, the database
name should be consistent with the current database naming convention.
Format – Database Content
Table names and column names should not contain a space character and should not
be the same as any Teradata reserved words. Please see reserved word list located at
http://tunweb.teradata.ws/tunweb/reservedwords.aspx. Space characters can be
removed or replaced with a “_” character. To avoid a conflict with a reserved word, a
“_t” can be added to table names and a “_c” can be added to column names.
The data to be loaded to Teradata should be in one of the following three formats:
1. Best Format -- SQL script with Create Table and Insert commands
A Windows ASCII text file or multiple files should contain the SQL with the Create
Table statement for each table including the primary index, and contain Insert
statements for the data for each table. If any secondary indexes are desired, then
the Create Index SQL statements should be included. The SQL statements
should use Teradata SQL syntax. The Teradata SQL Quick Reference User
Manual is available at
http://tunweb.teradata.ws/tunweb/TeradataUserManuals/Teradata_SQL_Quick_
Reference.pdf.
2. Second Best Format -- Microsoft Access Database
A single "mdb" file should contain all the tables needed for the database and
shouldn't contain any other tables. A Windows ASCII text file should list the
primary index for each table and list any desired secondary indexes. The best
method for giving the indexing information is to supply Create Table and Create
Index SQL statements using Teradata SQL syntax.
3. Another Format -- Create Table SQL and Data Files
A Windows ASCII text file or multiple files should contain the SQL for the Create
Table statement for each table including the primary index. If any secondary
indexes are desired, then the Create Index SQL statements should be included.
The SQL statements should use Teradata SQL syntax. For each table there
should be a Windows ASCII text file containing the data for the table. Each
record/line in the data file should contain the data for 1 row for the table. Data
records can be variable length with a delimiter or fixed length. Fixed length
records are preferred. For fixed length records, the number of characters for
each data item should be specified. For variable length records, the delimiter
character should be specified and should not appear in any of the data columns.
Quotes should not be placed around alpha fields. If the order of the data in each
text file record is different than the order of the columns in the table definition,
then the differences must be documented.
If you have questions about this process, please contact Stan Ozenbaugh at
stan.ozenbaugh@teradata.com.