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

Daniel,

I agree as I had not planned to have the "installation software" do the creation of the Oracle tables, but simply to have the SQL scripts (at least that's where I am at this point -- using scripts) to create and populate the tables in a folder on the CD.

The clients' own DBAs could then copy the files they needed from the installation CD and do what they need to do to create the tables with my supplied scripts. Since they would be supplied scripts, they could modify them as they deem appropriate within the guidelines that the application requires.

I definitely agree with giving the DBAs everything they need to feel comfortable running the scripts.

The installation program (created with VS.NET) will install the "application" and the necessary "setup" and "admin" consoles that the application needs to setup the "connection strings" in ADO.NET.

Thanks for the insight...

Ron

[Quoted] "Daniel Morgan" <damorgan_at_exxesolutions.com> wrote in message news:3F37BA12.82E6D800_at_exxesolutions.com...
>
>
> The Oracle software installation can not be done by your software. It must
be
> done as an independent step by a competent DBA working with a competent
> SysAdmin. From that point forward you can use a simple ASCII file script
to
> build the system tablespace, other tablespaces, create users, create
roles,
> create tables, populate them, etc. And it doesn't require documentation to
> figure out how to do this.
>
> Go to$ORACLE_HOME/admin/.../scripts on your server and the scripts for
database
> creation and tablespace builds are there: Just modify them. To create
tables,
> views, procedures, and populate them with data the scripts are at
> $ORACLE_HOME/rdbms/admin. Look specifically at sql.bsq, catalog.sql,
catproc.sql
> to see how.
>
> This isn't rocket science. It is elementary school and any Oracle shop
will know
> how it is done and expect to see it in this way.
>
> In fact many Oracle shops will refuse to let you install if you don't do
it this
> way because they will want to sign an NDA and review the scripts before
letting
> you run them on their server. I for one have never allowed a blind
installation
> on a server. If a vendor insists on doing that ... they lost the sale.
> --
> Daniel Morgan
> http://www.outreach.washington.edu/extinfo/certprog/oad/oad_crs.asp
> damorgan_at_x.washington.edu
> (replace 'x' with a 'u' to reply)
>
>
Received on Mon Aug 11 2003 - 23:50:19 CEST