Re: I can attach in SQL Server, but can I in Oracle?

Ross,

Thanks.

[Quoted] [Quoted] I looked at building a DTS package from SQL Server 2000 and was not comfortable with trying to get that implemented in a client's Oracle shop

I found articles and book chapters related to what you suggest and also found them way too horrifying to really impose on clients. I was hoping that there was an easier way that I was overlooking.

At the moment, I am inclined to do this with SQL Scripts for the Oracle installations.

Again, many thanks for the help and advice.

Ron

"Ross McKay" <rosko_at_zeta.NOT.THIS.BIT.org.au> wrote in message news:34h8jvcpr3ua248hg8rdkd4khftcpd5i0n_at_4ax.com...
> G'day Ron,
>
> On Fri, 08 Aug 2003 18:00:28 GMT, "Ron Fluegge" <rmflugge_at_swbell.net>
> wrote:
>
> >...
> >(1) Create copies of the tablespace (database in SQL Server terminology)
> >required for the application (not only the schema, but also one "table"
> >contains about 5,000 records that need to be a part of the installation
so
> >it appears to be more than a SQL script to create the tables)
> >
> >(2) Copy the files created in (1) to the distribution CD
> >
> >(3) Clients then copy the files created in (1) to their own Oracle server
> >and then "attach" these files to the database instance so that the
> >application can then access the tables.
> >...
>
> Having read through the other responses (trying to ignore Sybrand's as
> usual), I reckon Karsten comes closest to what you asked for.
>
> However, another method you might want to consider (given your
> predilection for Microsoft technologies and existing experience with
> DTS) is to create a DTS package on-the-fly and populate the target
> database from either text-based data files or even (shudder!) a Jet .mdb
> file on your CD. You could then use a single set of source data (text
> files, .mdb, whatever) to populate whichever target database you are
> installing for (SQL Server, Sybase, Oracle, whatever...).
>
> Your installer program could conditionally build the DTS package to
> suit, based on target database and also user-selected options.
>
> Steps would be something like:
> a) user installs their desired database product
> b) user follows your instructions for creating target
> database/schema/etc.
> c) your installation program creates and executes DTS package, which
> establishes the tables, imports the data, creates indices and
> constraints, and establishes SP's/packages etc
>
> You could even handle step b) within your installer program too.
>
> If you are unsure of using DTS like this, take a good squiz at
>
> www.sqldts.com
>
> or send me an email privately.
>
> cheers,
> Ross.
> --
> Ross McKay, WebAware Pty Ltd
> "Since when were you so generously inarticulate?" - Elvis Costello
>
Received on Sat Aug 09 2003 - 03:57:12 CEST