Re: DB Setup - Dump file versus SQL Loader

From: Frank van Bortel <frank.van.bortel_at_gmail.com>
Date: Fri, 08 Jun 2007 20:37:12 +0200
Message-ID: <f4c7kn$a05$1@news6.zwoll1.ov.home.nl>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

AnGanesh wrote:
> Dear All,
>
> I am working for a product based company. For DB setup for our
> product, we are currently using the dump file to generate all the
> required tables and initial data. As part of initial data setup, we
> have both static/lookup data loading and test data loading as well
> (nearly 130 tables have data setup).
>

Lots of employers do *not* accepts dumps - there is no way of checking beforehand what they contain.

lots of DBAs want control, too - they want the stuff in a tablespace called "XYZ", because that is the naming standard. Not the "image_blob_ts" you use...

There are probably more of these arguments, and you came up with one yourself: maintainability!

-- Regards, Frank van Bortel

Top-posting is one way to shut me up...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)

iD8DBQFGaaHYLw8L4IAs830RAm8IAKCFzPGUWzyN9JKmqcWOcxid9RbpcgCfXz2b BLkJQ8KMmJ0t0CJZj+EWw6Q=
=XR1I
-----END PGP SIGNATURE----- Received on Fri Jun 08 2007 - 13:37:12 CDT