Re: scripts "create table" ddl statement

"Howard J. Rogers" wrote:

> Version?????????????????????????
>

There are many possible reasons and as many solutions. While some solutions are generic, some solutions have been created to address specific issues. So I'd add "Purpose/Reason?????" here!

> I only ask, because in 9i there's a package to do precisely this. Which I
> would explain in more detail if I thought for one minute it might be
> applicable to you... but since you leave me guessing, it hardly seems
> worthwhile.
>

A legitimate sentiment. (But it seems we do get a bit cranky as the day wears on.)

>
> Otherwise, and for all versions, do an export, and then an import with
> rows=n. indexes=n, indexfile=blah.txt ignore = y. You'll produce a text file
> called blah.txt which contains the entire DDL statement for any tables
> included in the original export.

I suspect many here have coded those scripts by hand at least once over the years. It's not really a big issue. However, as Howard points out, "export" ensures that the DDL is built and furthermore that it is consistent with the version. And "import" can be used to move the DDL to other schemas or even databases. The export file can be viewed using a normal editor.

OEM can be used to display the DDL which, in many environments, can be cut & paste or modified directly. And OEM extension Change Management Pack, does the DDL (but for a price).

/Hans Received on Thu Mar 27 2003 - 09:25:38 CST