Re: Best Practices on DB2 SQL Databases

I agree that best practice should be to generate tables in SQL. DDS is a
dead horse now. Everything is being done in DDL and the performance issues.
Also, you don't have constraints in DDS or Primary keys. The hassle is
maintaining some degree of compatibility with the old world.

Also, people had suggested doing an ALTER table once the table is created to
change names but not supported or at least through Ops Nav and since Ops Nav
just generates an SQL to do the ALTER it probably not supported in
SQL.Checked and it is not.

ALTER is pretty limited. Will only add fields to end of table. I always end
up saving data and recreating when I update an SQL table definition.

On Wed, Jan 14, 2009 at 10:28 AM, Walden H. Leverich <
WaldenL@xxxxxxxxxxxxxxx> wrote:

Today's ORM tools prefer to generate database objects as well.

Only if you let them. :-) I'm a DB wonk, I want control of my DB!

--
Walden H Leverich III
Tech Software
(516) 627-3800 x3051
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com

Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.