Re: How do I ensure order of rows loaded by SQL Loader?

Hi Michael !

   Of course I understand the importance of normalized data. Actually the table in which I am loading the data is just a temporary table. There are a lot of validations to be performed on the data in the 'as is' format. That's why I've loaded them into a single table. Once the data passes the validations I've written an oracle procedure that reads the data from this table and enters them into some 6-7 normalized tables. The temp table data is then deleted. Straightway entering the data from SQL Loader to these tables would have been difficult.
So I've not lost out on the 'normalization' part.

Puneet

"Michael J. Moore" <NOhicamelSPAM_at_comcast.net> wrote in message news:<J0Otb.167960$ao4.543251_at_attbi_s51>...
> I know that this is a dead issue but I have to wonder why you did not follow
> Joel's advice and "normalize" the data. Maybe you had a good reason but too
> often I see people adding sequence numbers when what they should have done
> is reduced the data to 3rd normal form and created tables and constraints
> accordingly.
>
> With your solution, your programmers will now have to code logic to detect
> if there are any 'associates' before attempting to delete a 'contact' -
> delete anomaly, and detect if there is a corresponding 'contact' before
> inserting an 'associate' - update anomaly. Also you now have issues of what
> happens when associates are delete leaving a gap in your sequence numbers.
>
> Maybe your data is static so you don't have to worry about these problems.
> If so, you are home free. But if programmers need to maintain this data with
> updates, inserts and deletes, you have placed a heavy burden on them by not
> normalizing the data.
>
> Regards,
> Mike
>
>
Received on Mon Nov 17 2003 - 00:30:44 CST