|
AAARRRGGGGHHHH!!!!! Guess what it wasn't the "Legacy" machine.. Unbeknownst to anyone still here, the automagic process on the SQL server to populate the "directory" actually does the following: 1. Imports the "Entire" Main Table from the iseries to the SQL Server 2. Imports all the secondary tables from the iSeries to the SQL Server 3. If "certain" criteria are met on the import of some of the secondary tables then the SQL server does a DELETE from Main Table imported in step 1. (the person in question met 1 of those criteria---> actually had 56 difference in the iSeries file and the Main table AFTER this step, all of them met one of the "delete" criteria 4. The SQL Server then uses the really UGLY SQL I mentioned earlier to populate the directory using the tables imported to the SQL server. YUCK!!!!!! On 11/29/06, Elvis Budimlic <ebudimlic@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Well, change it to something iSeries will allow and mere humans can understand :) -----Original Message----- Subject: Re: SQL from MS SQL Server Sadly its a REAL column name -- 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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.