As your university already has Oracle, I guess it would be OK if you really use it.
Primary goal - design of the database - doesn't seem to be too complicated. First idea is to create three tables to store a) site data, b) subsite data, c) temperature data. Just as a first aid, try something like this:
Code:
create table site
(site_id number(3),
site_name varchar2(30));
create table subsite
(sub_id number(3),
sub_name varchar2(30));
create table temperature
(site_id number(3),
sub_id number(3),
time_stamp date,
temp_value number(5, 2));
Please note that this is just a scratch - I believe real model will be much richer in description, number of tables and fields within. Furthermore, I didn't create constraints, indexes etc. just to keep it simple. Read more about Oracle SQL
here, while all books index can be found
here.
How are you going to fill data into the tables? "Site" and "Subsite" are easy - you fill them once and that's it. But, what about "Temperature"? You'll have an operater whose job will be to do it? I guess not! Have data delivered from the subsite and then loaded into your table(s)?
Querying this tables is quite simple; I'm not familiar with the .csv extension, but if it is a flat text file, spooling results of the query would do it.
Secondary goals ... well, I'm afraid I can't help much you about this. If you use Oracle Developer Suite 9i, which is web-oriented (so forms and reports are run and displayed through internet browser), I guess it wouldn't be too complicated to have that kind of a web access. And SAS ... I really don't know anything about it, but - if it uses ODBC - there shouldn't be too many problems.
If I may add to this ...
no Oracle experience, 6 months deadline and budget of $200 smell like a nightmare to me. Good luck, anyway. You'll need it
P.S. Let us know about the progress of your project. Could be interesting to participate in it, even though by the mean of this Forum. There are many DB
wizards here which will be happy to help you with the project.