Using SQL Server Script to create Oracle DB Schema

Question

Hi,
I have a SQL Server script which does a few things such as creating databases (after dropping), creating tables etc. Now I want to replicate the SQL Server databases and their tables etc in an Oracle9i DB. How would a SQL Server script compare to an Oracle script? i.e. what differences are there? and how would I have to alter the script to have it work on Oracle?
As an example, my SQL Server script would look something like this:
DROP DATABASE test1;
DROP DATABASE test2;
CREATE DATABASE test1;
CREATE DATABASE test2;
GO;
USE test1;
CREATE TABLE Table1 (
TableOneID INT IDENTITY PRIMARY KEY NOT NULL,
Name VARCHAR(255) NOT NULL,
PRIMARY KEY(TableOneID));
CREATE TABLE Table2 (
TableTwoID INT IDENTITY NOT NULL,
TableOneID INT NOT NULL,
PRIMARY KEY(TableTwoID, TableOneID),
FOREIGN KEY(TableOneID) REFERENCES Table1(TableOneID));
USE test2;
CREATE TABLE ....
etc...
thanks!

Answer 1

Also I think
CREATE TABLE table1
( tableoneid INT PRIMARY KEY NOT NULL
, name VARCHAR(255) NOT NULL
, PRIMARY KEY(tableoneid) );should probably be
CREATE TABLE table1
( tableoneid INT CONSTRAINT table1_pk PRIMARY KEY
, name VARCHAR(255) NOT NULL );otherwise you specify the primary key twice (and PRIMARY KEY implies NOT NULL so the NOT NULL is redundant).
Then TABLE2 might need to be something like:
CREATE TABLE table2
( tabletwoid INT NOT NULL
, tableoneid NOT NULL CONSTRAINT table2_table1_fk REFERENCES table1
, CONSTRAINT table2_pk PRIMARY KEY(tabletwoid, tableoneid) );although the table-level constraint syntax could be used for the foreign keys if it meant less editing of your scripts. The "CONSTRAINT constraintname" clause of constraints is optional but recommended, as otherwise they will get system-generated names like "SYS_C005157". (Note that if you specify the FK inline as part of the column definition you do not need to include a datatype.)
If the IDENTITY clause causes a sequential value to be assigned as a default, there is no direct equivalent to that in Oracle. The nearest thing would be a row-level BEFORE INSERT trigger.