"Brian Elliott" <NotForSpam@AskIfUWant> wrote in message
news:471b6c5d$1@news.povray.org...

> Selecting from tables, their column definitions and table data are only a
> small part of getting the data and structure out:  I have to get the
entire
> application out.  I would also have to make SQL to recreate:
>
> Table type (heap, index-organised, cluster, partition) Definitions of all
> indexes and constraints on each table, foreign-key constraints to other
> tables, tablespace and storage info, remembering again to do the same for
> each of its indexes.
>
> Triggers on the tables -- PL/SQL code that fires before/after an
> insert/update/delete.
> Sequences, including the number they are now at. (So new sequences are
> created from that starting point instead of starting at one)
>
> Views -- named SQL that can be selected and joined as one uses a table in
> most places.
> The program code stored in PL/SQL functions, procedures and packages.
>
> Jobs.  Ugh, I know the least about these.  I'm sure OEM will have job
> schedules registered in the database engine.
>

Dunnon about Oracle, but in MS SQL, all of those are stored in tables as
well and are scriptable, providing you know the right tables.

Post a reply to this message